Social network communities

ABSTRACT

Disclosed are methods, apparatus, systems, and computer-readable storage media for providing communities of users in an online social network. In some implementations, a plurality of user identities (IDs) is maintained on one or more storage media. The user IDs include first user IDs identifying first users belonging to a first community associated with a first organization and second user IDs identifying second users belonging to a second community. A server receives a request to access the second community from a computing device associated with a user. When it is determined that the computing device has established access to the first community, the one or more storage media can be accessed to determine that the user ID is one of the second user IDs. Then, social network data available to the second users can be sent to the computing device.

PRIORITY DATA

This patent document claims priority to co-pending and commonly assignedU.S. Provisional Patent Application No. 61/614,832, titled “ChatterCommunity”, by Lai et al., filed on Mar. 23, 2012 (Attorney Docket No.835PROV), which is hereby incorporated by reference in its entirety andfor all purposes.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material,which is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

TECHNICAL FIELD

This patent document relates generally to providing on-demand servicesin an online social network using a database system and, morespecifically, to techniques for associating users of the social network.

BACKGROUND

“Cloud computing” services provide shared resources, software, andinformation to computers and other devices upon request. In cloudcomputing environments, software can be accessible over the Internetrather than installed locally on in-house computer systems. Cloudcomputing typically involves over-the-Internet provision of dynamicallyscalable and often virtualized resources. Technological details can beabstracted from the users, who no longer have need for expertise in, orcontrol over, the technology infrastructure “in the cloud” that supportsthem.

Database resources can be provided in a cloud computing context.However, using conventional database management techniques, it isdifficult to know about the activity of other users of a database systemin the cloud or other network. For example, the actions of a particularuser, such as a salesperson, on a database resource may be important tothe user's boss. The user can create a report about what the user hasdone and send it to the boss, but such reports may be inefficient, nottimely, and incomplete. Also, it may be difficult to identify otherusers who might benefit from the information in the report.

BRIEF DESCRIPTION OF THE DRAWINGS

The included drawings are for illustrative purposes and serve only toprovide examples of possible structures and operations for the disclosedinventive systems, apparatus, methods and computer-readable media forproviding communities of users in an online social network. Thesedrawings in no way limit any changes in form and detail that may be madeby one skilled in the art without departing from the spirit and scope ofthe disclosed implementations.

FIG. 1 shows a system diagram of an example of a social networkingenvironment 100 with communities according to some implementations.

FIG. 2 shows a flowchart of an example of a computer implemented method200 for providing access to communities of users in an online socialnetwork, performed in accordance with some implementations.

FIG. 3 shows a system diagram of an example of a social networkingenvironment 300 with communities according to some implementations.

FIG. 4 shows an example of a user identity (ID) mapping table 400identifying communities to which a user can be provided access,according to some implementations.

FIG. 5 shows an example of a privileges table 500 identifying rights andrestrictions of users to access data and initiate actions in one or morecommunities according to one or more attributes, according to someimplementations.

FIG. 6 shows an example of a privileges table 600 identifying differentaccess models governing permissions of users to access data and initiateactions in one or more communities according to one or more attributes,according to some implementations.

FIG. 7 shows an example of an access model customization window 700 asdisplayed in a graphical user interface (GUI) on a display device,according to some implementations.

FIG. 8 shows a flowchart of an example of a computer implemented method800 for providing communities in an online social network, performed inaccordance with some implementations.

FIG. 9 shows a flowchart of an example of a computer implemented method900 for providing communities in an online social network, performed inaccordance with some implementations.

FIG. 10 shows a flowchart of an example of a computer implemented method1000 for initiating and managing sessions with communities in an onlinesocial network, performed in accordance with some implementations.

FIGS. 11-30 show examples of pages in the form of GUIs as displayed ondisplay devices for interacting with communities in an online socialnetwork, according to some implementations.

FIG. 31A shows a block diagram of an example of an environment 10 inwhich an on-demand database service can be used in accordance with someimplementations.

FIG. 31B shows a block diagram of an example of some implementations ofelements of FIG. 31A and various possible interconnections between theseelements.

FIG. 32A shows a system diagram illustrating an example of architecturalcomponents of an on-demand database service environment 3200 accordingto some implementations.

FIG. 32B shows a system diagram further illustrating an example ofarchitectural components of an on-demand database service environmentaccording to some implementations.

DETAILED DESCRIPTION

Examples of systems, apparatus, and methods according to the disclosedimplementations are described in this section. These examples are beingprovided solely to add context and aid in the understanding of thedisclosed implementations. It will thus be apparent to one skilled inthe art that implementations may be practiced without some or all ofthese specific details. In other instances, certain process/methodoperations, also referred to herein as “blocks,” have not been describedin detail in order to avoid unnecessarily obscuring implementations.Other applications are possible, such that the following examples shouldnot be taken as definitive or limiting either in scope or setting.

In the following detailed description, references are made to theaccompanying drawings, which form a part of the description and in whichare shown, by way of illustration, specific implementations. Althoughthese implementations are described in sufficient detail to enable oneskilled in the art to practice the disclosed implementations, it isunderstood that these examples are not limiting, such that otherimplementations may be used and changes may be made without departingfrom their spirit and scope. For example, the blocks of methods shownand described herein are not necessarily performed in the orderindicated. It should also be understood that the methods may includemore or fewer blocks than are indicated. In some implementations, blocksdescribed herein as separate blocks may be combined. Conversely, whatmay be described herein as a single block may be implemented in multipleblocks.

Various implementations described or referenced herein are directed todifferent systems, apparatus, methods and computer-readable storagemedia for defining, maintaining, and providing access to communities ofusers in an online social network, also referred to herein as a socialnetworking system. One example of an online social network is Chatter®,provided by salesforce.com, inc. of San Francisco, Calif.salesforce.com, inc. is a provider of social networking services,customer relationship management (CRM) services and other databasemanagement services. These various services can be provided in a cloudcomputing environment, for example, in the context of a multi-tenantdatabase system. Different communities of users can be created andmanaged in such an environment without having to install softwarelocally, that is, on computing devices of users accessing thecommunities. While the disclosed implementations are often describedwith reference to Chatter®, those skilled in the art should understandthat the disclosed systems, apparatus, methods and computer-readablestorage media can be implemented in the context of one or more othersocial networking systems, such as Facebook®, LinkedIn°, Twitter®,Google+®, Yammer® and Jive®.

Some implementations of the disclosed systems, apparatus, methods andcomputer-readable storage media are configured to provide communities ofusers in an online social network. Such communities are to bedifferentiated from “groups” of users in Chatter®, described in greaterdetail below. That is, a community of users can exist as an entity apartfrom and in addition to any group or groups of such users in the socialnetwork, although some of the rights and restrictions provided to acommunity member may be the same or similar as those provided to amember of a group.

In some implementations, a community can be defined as a secure spacefor different stake-holders of an organization, such as employees,customers and partners of the organization, to collaborate with oneanother by accessing shared data, interacting with community-centrictasks and business processes, and using conversational services such aschat sessions, feed-based communication, and private messaging. Thecommunity can be structured and maintained as a public or private spacefor users having different relationships with the organization, so theusers can converse and collaborate in an effective manner. The users canbe of different types, such as internal or external, and/or the userscan have different roles, such as employee, customer or partner, withsuch types and roles defining a user's relationship with theorganization. For example, a partner can be an entity external to anorganization that sells services and/or provides support on behalf of anemployee, who is an internal user of the organization. Multiplecommunities can be implemented, some affiliated with differentorganizations, and a user can navigate across the communities in aseamless fashion from the user's perspective.

In some instances, the community can provide various collaboration toolsin a branded environment, for example, with community-specific web pagesproviding names, trademarks, themes, colors and other indicia ofproducts, services, and/or an organization offering the product orservice. Thus, a community can be a space with a branded look-and-feelfor people to collaborate on data pertaining to the community and oftenpertaining to an organization with which the community is affiliated.

Each community can be structured so a community leader, systemadministrator or other user having appropriate security clearance candefine rules governing community membership and privileges governing: i)access and use of various community data, ii) the ability to take actionand cause events to occur in relation to the community, and iii) thevisibility of users to each other. These various privileges can bedefined and customized at a granular level, for instance, with differentaccess rights and restrictions configured on a per-user or per-type ofuser basis, on a per-data item or per-type of data basis, and/or on aper-action or per-type of action basis.

In some instances, a user can have different user profiles for differentcommunities. In other instances, a user can have a primary user profileand can select which fields of the profile are to be exposed to eachcommunity of which the user is a member. In some implementations, auser's community profile has a child-parent relationship with theprimary profile and is tailored to inherit data from selected fields ofthe primary profile.

In some instances, a community can be open, as is often the case withpublic communities, in that there are no or minimal restrictions onusers to access data, initiate actions, and view other communitymembers' profiles, regardless of user type or role with respect to anorganization. Thus, in a public community, employees, customers andpartners of an organization affiliated with the community can freelyview community data and each other's profiles, follow the same objects,and converse using the same feeds, by virtue of being members of thesame community.

In some implementations of the disclosed communities, the same useridentity (ID), such as a login name or email address assigned to a givenuser, can be used by a user to directly log in and thus gain access to acommunity, that is, without requiring the user to separately log in tothe social networking system hosting the community, as well as allow theuser navigate across multiple communities during a web browsing session.Thus, for example, a user is not required to supply login credentialseach time the user clicks through a web page of a first community to apage of a second community. A single user ID can be used to navigateacross various communities, some of which can belong to differentorganizations.

In some implementations, full collaboration in a community is possibleregardless of user type or role. Internal and external users can beprovided with full access or the same level of restricted access to thesame feeds available through the community, and such users can view eachother's walls and follow each other. The various types and/or roles ofusers can have the same rights to access and edit CRM records such asopportunities, leads, contacts, accounts, cases, etc. and collaboratewith each other regarding such data using feeds. CRM data and files cantraverse community boundaries, that is, such that members of differentcommunities may have privileges to access and interact with the same CRMrecords.

The branding of a community can include custom network addresses such asuniform resource locators (URLs) with brand names included in a stringof characters defining the URL. Thus, each community provided in anonline social network can have a unique and branded URL customized torefer to a product, service, and/or organization by brand name. Thebranding of a community can also or alternatively include themes andcolor options presented as parts of one or more community pages toprovide a look-and-feel identifying a brand of an organization. Thenavigation options for community pages can also be customized to includespecific tabs and other components presented in a graphical userinterface (GUI) that identify a brand or aspects of a brand associatedwith an organization.

Branding data in a community can be different from and can exclude anybrands of the social networking system hosting the community. Forinstance, a community maintained in Chatter® can have pages with logos,themes and color schemes identifying an organization such as Burberry®,with which the community is affiliated, while the pages specificallyexclude any logos, slogans or graphical images identifying Chatter® orsalesforce.com. In this example, the Burberry® logos, themes and colorschemes can be retrieved from the Burberry® website. Other communitiescan similarly include branding of other organizations, even though allof the communities are maintained on a social networking system providedby salesforce.com, inc. or another social network provider.

The sharing of files and visibility of users and user-submitted messagescan be customized according to who is the user attempting to access suchdata, who is the user owning or having submitted the data, what is thetype of data file or message, and/or what is the action requested withrespect to the data. One community member may have limited privileges toaccess .doc documents but may be prevented from accessing .xls documentsand CRM records. Another member of the same community may have unlimitedprivileged to access and interact with these documents and records.Different rights and restrictions with respect to viewing andinteracting with feed items in a feed can be similarly custom-tailoredfor different users or types of users in a given community.

File libraries can be maintained, where a type or role of user isgranted access to a library and, thus, is granted access to all of thefiles in that library. In some implementations, external users can berestricted from editing the content of such files, while internal userscan freely do so. In some community implementations, file collaborationand editing privileges can be granted to both external and internalusers, and users have the ability to choose whether to upload or share afile or other data in a community, knowing that other various types ofusers within the community would have the ability to freely view,collaborate about, and edit that data. In some instances, a communitycan be configured to prevent certain users from sharing files outside ofthe community. Thus, a file could be accessible in community A and notin community B. Additionally, one file may be public—viewable by usershaving various roles and/or types—in community A, but beprivate—viewable only by users having specified roles and/or types—incommunity B.

In some implementations, a system administrator defines who can see whomin a community. The community can be configured to have an open model inwhich every member can see every other member's profile and/or contactinformation. In other instances, a community can have a more restrictedmodel, for instance, in which external users can view other externalusers' profiles but be blocked from accessing or viewing internal users'profiles and/or contact information. Such access models can be extendedto determine which feeds, feed items, records, record updates, groupsand other social network constructs a particular type or role of usercan access.

These and other implementations may be embodied in various types ofhardware, software, firmware, and combinations thereof. For example,some techniques disclosed herein may be implemented, at least in part,by computer-readable media that include program instructions, stateinformation, etc., for performing various services and operationsdescribed herein. Examples of program instructions include both machinecode, such as produced by a compiler, and files containing higher-levelcode that may be executed by a computing device such as a server orother data processing apparatus using an interpreter. Examples ofcomputer-readable media include, but are not limited to, magnetic mediasuch as hard disks, floppy disks, and magnetic tape; optical media suchas CD-ROM disks; magneto-optical media; and hardware devices that arespecially configured to store program instructions, such as read-onlymemory (“ROM”) devices and random access memory (“RAM”) devices. Theseand other features of the disclosed implementations will be described inmore detail below with reference to the associated drawings.

Online social networks are increasingly becoming a common way tofacilitate communication among people who can be recognized as users ofa social networking system. Some online social networks can beimplemented in various settings, including organizations, e.g.,enterprises such as companies or business partnerships, academicinstitutions, or groups within such an organization. For instance,Chatter® can be used by employee users in a division of a businessorganization to share data, communicate, and collaborate with each otherfor various purposes.

In some online social networks, users can access one or more informationfeeds, which include information updates presented as items or entriesin the feed. Such a feed item can include a single information update ora collection of individual information updates. A feed item can includevarious types of data including character-based data, audio data, imagedata and/or video data. An information feed can be displayed in agraphical user interface (GUI) on a display device such as the displayof a computing device as described below. The information updates caninclude various social network data from various sources and can bestored in an on-demand database service environment. In someimplementations, the disclosed methods, apparatus, systems, andcomputer-readable storage media may be configured or designed for use ina multi-tenant database environment.

In some implementations, an online social network may allow a user tofollow data objects in the form of records such as cases, accounts, oropportunities, in addition to following individual users and groups ofusers. The “following” of a record stored in a database, as described ingreater detail below, allows a user to track the progress of thatrecord. Updates to the record, also referred to herein as changes to therecord, are one type of information update that can occur and be notedon an information feed such as a record feed or a news feed of a usersubscribed to the record. Examples of record updates include fieldchanges in the record, updates to the status of a record, as well as thecreation of the record itself. Some records are publicly accessible,such that any user can follow the record, while other records areprivate, for which appropriate security clearance/permissions are aprerequisite to a user following the record.

Information updates can include various types of updates, which may ormay not be linked with a particular record. For example, informationupdates can be user-submitted messages or can otherwise be generated inresponse to user actions or in response to events. Examples of messagesinclude: posts, comments, indications of a user's personal preferencessuch as “likes” and “dislikes”, updates to a user's status, uploadedfiles, and hyperlinks to social network data or other network data suchas various documents and/or web pages on the Internet. Posts can includealpha-numeric or other character-based user inputs such as words,phrases, statements, questions, emotional expressions, and/or symbols.Comments generally refer to responses to posts, such as words, phrases,statements, answers, questions, and reactionary emotional expressionsand/or symbols. Multimedia data can be included in, linked with, orattached to a post or comment. For example, a post can include textualstatements in combination with a JPEG image or animated image. A like ordislike can be submitted in response to a particular post or comment.Examples of uploaded files include presentations, documents, multimediafiles, and the like.

Users can follow a record by subscribing to the record, as mentionedabove. Users can also follow other entities such as other types of dataobjects, other users, and groups of users. Feed tracked updatesregarding such entities are one type of information update that can bereceived and included in the user's news feed. Any number of users canfollow a particular entity and thus view information updates pertainingto that entity on the users' respective news feeds. In some socialnetworks, users may follow each other by establishing connections witheach other, sometimes referred to as “friending” one another. Byestablishing such a connection, one user may be able to see informationgenerated by, generated about, or otherwise associated with anotheruser. For instance, a first user may be able to see information postedby a second user to the second user's personal social network page. Oneimplementation of such a personal social network page is a user'sprofile page, for example, in the form of a web page representing theuser's profile. In one example, when the first user is following thesecond user, the first user's news feed can receive a post from thesecond user submitted to the second user's profile feed, also referredto herein as the user's “wall,” which is one example of an informationfeed displayed on the user's profile page.

In some implementations, an information feed may be specific to a groupof users of an online social network. For instance, a group of users maypublish a news feed. Members of the group may view and post to thisgroup feed in accordance with a permissions configuration for the feedand the group. Information updates in a group context can also includechanges to group status information.

In some implementations, when data such as posts or comments input fromone or more users are submitted to an information feed for a particularuser, group, object, or other construct within an online social network,an email notification or other type of network communication may betransmitted to all users following the user, group, or object inaddition to the inclusion of the data as a feed item in one or morefeeds, such as a user's profile feed, a news feed, or a record feed. Insome online social networks, the occurrence of such a notification islimited to the first instance of a published input, which may form partof a larger conversation. For instance, a notification may betransmitted for an initial post, but not for comments on the post. Insome other implementations, a separate notification is transmitted foreach such information update.

The term “multi-tenant database system” can refer to those systems inwhich various elements of hardware and software of a database system maybe shared by one or more customers. For example, a given applicationserver may simultaneously process requests for a great number ofcustomers, and a given database table may store rows of data such asfeed items for a potentially much greater number of customers. The term“query plan” generally refers to one or more operations used to accessinformation in a database system.

A “user profile” or “user's profile” is generally configured to storeand maintain data about a given user of the database system. The datacan include general information, such as name, title, phone number, aphoto, a biographical summary, and a status, e.g., text describing whatthe user is currently doing. As mentioned below, the data can includemessages created by other users. Where there are multiple tenants, auser is typically associated with a particular tenant. For example, auser could be a salesperson of a company, which is a tenant of thedatabase system that provides a database service.

The term “record” generally refers to a data entity, such as an instanceof a data object created by a user of the database service, for example,about a particular (actual or potential) business relationship orproject. The data object can have a data structure defined by thedatabase service (a standard object) or defined by a user (customobject). For example, a record can be for a business partner orpotential business partner (e.g., a client, vendor, distributor, etc.)of the user, and can include information describing an entire company,subsidiaries, or contacts at the company. As another example, a recordcan be a project that the user is working on, such as an opportunity(e.g., a possible sale) with an existing partner, or a project that theuser is trying to get. In one implementation of a multi-tenant databasesystem, each record for the tenants has a unique identifier stored in acommon table. A record has data fields that are defined by the structureof the object (e.g., fields of certain data types and purposes). Arecord can also have custom fields defined by a user. A field can beanother record or include links thereto, thereby providing aparent-child relationship between the records.

The terms “information feed” and “feed” are used interchangeably hereinand generally refer to a combination (e.g., a list) of feed items orentries with various types of information and data. Such feed items canbe stored and maintained in one or more database tables, e.g., as rowsin the table(s), that can be accessed to retrieve relevant informationto be presented as part of a displayed feed. The term “feed item” (orfeed element) refers to an item of information, which can be presentedin the feed such as a post submitted by a user. Feed items ofinformation about a user can be presented in a user's profile feed ofthe database, while feed items of information about a record can bepresented in a record feed in the database, by way of example. A profilefeed and a record feed are examples of different information feeds. Asecond user following a first user and a record can receive the feeditems associated with the first user and the record for display in thesecond user's news feed, which is another type of information feed. Insome implementations, the feed items from any number of followed usersand records can be combined into a single information feed of aparticular user.

As examples, a feed item can be a message, such as a user-generated postof text data, and a feed tracked update to a record or profile, such asa change to a field of the record. Feed tracked updates are described ingreater detail below. A feed can be a combination of messages and feedtracked updates. Messages include text created by a user, and mayinclude other data as well. Examples of messages include posts, userstatus updates, and comments. Messages can be created for a user'sprofile or for a record. Posts can be created by various users,potentially any user, although some restrictions can be applied. As anexample, posts can be made to a wall section of a user's profile page(which can include a number of recent posts) or a section of a recordthat includes multiple posts. The posts can be organized inchronological order when displayed in a graphical user interface (GUI),for instance, on the user's profile page, as part of the user's profilefeed. In contrast to a post, a user status update changes a status of auser and can be made by that user or an administrator. A record can alsohave a status, the update of which can be provided by an owner of therecord or other users having suitable write access permissions to therecord. The owner can be a single user, multiple users, or a group. Inone implementation, there is only one status for a record.

In some implementations, a comment can be made on any feed item. In someimplementations, comments are organized as a list explicitly tied to aparticular feed tracked update, post, or status update. In someimplementations, comments may not be listed in the first layer (in ahierarchal sense) of feed items, but listed as a second layer branchingfrom a particular first layer feed item.

A “feed tracked update,” also referred to herein as a “feed update,” isone type of information update and generally refers to data representingan event. A feed tracked update can include text generated by thedatabase system in response to the event, to be provided as one or morefeed items for possible inclusion in one or more feeds. In oneimplementation, the data can initially be stored, and then the databasesystem can later use the data to create text for describing the event.Both the data and/or the text can be a feed tracked update, as usedherein. In various implementations, an event can be an update of arecord and/or can be triggered by a specific action by a user. Whichactions trigger an event can be configurable. Which events have feedtracked updates created and which feed updates are sent to which userscan also be configurable. Messages and feed updates can be stored as afield or child object of the record. For example, the feed can be storedas a child object of the record.

A “group” is generally a collection of users. In some implementations,the group may be defined as users with a same or similar attribute, orby membership. In some implementations, a “group feed”, also referred toherein as a “group news feed”, includes one or more feed items about anyuser in the group. In some implementations, the group feed also includesinformation updates and other feed items that are about the group as awhole, the group's purpose, the group's description, and group recordsand other objects stored in association with the group. Threads ofinformation updates including group record updates and messages, such asposts, comments, likes, etc., can define group conversations and changeover time.

An “entity feed” or “record feed” generally refers to a feed of feeditems about a particular record in the database, such as feed trackedupdates about changes to the record and posts made by users about therecord. An entity feed can be composed of any type of feed item. Such afeed can be displayed on a page such as a web page associated with therecord, e.g., a home page of the record. As used herein, a “profilefeed” or “user's profile feed” is a feed of feed items about aparticular user. In one example, the feed items for a profile feedinclude posts and comments that other users make about or send to theparticular user, and status updates made by the particular user. Such aprofile feed can be displayed on a page associated with the particularuser. In another example, feed items in a profile feed could includeposts made by the particular user and feed tracked updates initiatedbased on actions of the particular user.

FIG. 1 shows a system diagram of an example of a social networkingenvironment 100 with communities according to some implementations. InFIG. 1, a social networking system 104 includes any number of computingdevices such as servers 108 a and 108 b. The servers 108 a and 108 b arein communication with one or more storage mediums configured to storeand maintain relevant data used to perform some of the techniquesdisclosed herein. In this example, the storage mediums include a user IDdatabase 112 and a privileges database 116. The user ID database 112 canmaintain lists of IDs of users who are members of respectivecommunities. By way of example, a “Community 1 User IDs” table 120 indatabase 112 includes a list of IDs of users who are members ofCommunity 1, a “Community 2 User IDs” table 124 lists IDs of users whoare members of Community 2, and so forth.

In FIG. 1, the privileges database 116 is configured to store privilegeinformation identifying or specifying access rights and restrictions ofusers according to various attributes such as a specified user ID, typeof user, role of user, type of community to which the user belongs,and/or a particular organization on behalf of which a community ismaintained. Such privilege information can be customized and edited asdescribed in greater detail below.

In FIG. 1, the social networking system servers 108 are configured tomaintain one or more communities of users such as communities 128, 132and 136 by interacting with databases 112 and 116 to identify members ofthose communities and privileges of members of a given community. Anynumber of users such as users 140 a, 140 b and 140 c can be serviced bysocial networking system 104. That is, any such users 140 can have userIDs and other relevant data such as user profiles maintained in socialnetworking system 104. By leveraging the information stored in storagemediums such as user ID database 112 and privileges database 116,communities 128, 132 and 136 of such users 140 can be defined. Thus, inthis example, the community 128 includes users 140 a, community 132includes users 140 b, and community 136 includes users 140 c and one ofusers 140 b. Thus, one of the users 140 b is a member of bothcommunities 132 and 136. When any such users 140 log in directly to acommunity, bypassing login pages of social networking system 104, or login via social networking system 104 using a suitable computing devicesuch as a laptop, tablet or smartphone, such users can be allowed toaccess data and take one or more actions available through socialnetworking system 104 as permitted by the relevant privilege informationstored in privileges database 116.

In FIG. 1, each of the communities 128, 132 and 136 is operated onbehalf of a different organization. In this example, community 128 isoperated on behalf of Org A, which in this example is Acme, Inc. Forexample, the users 140 a in community 128 may be employees, customersand/or partners of Acme, Inc. By the same token, the community 132 isoperated on behalf of Org B, which can be any type of organization asdescribed in greater detail below. The community 136 is maintained onbehalf of Org C. The various users in a given community can havedifferent relationships with the organization on behalf of which thecommunity is maintained. Thus, one or more of the users 140 b can be anemployee, customer or business partner of Org B. In this example, asmentioned above, one of the users 140 b is a member of both communities132 and 136. Thus, this user 140 b could be an employee of Org B and acustomer of Org C by way of example.

In FIG. 1, each community 128, 132 and 136 often has one or more pagesof relevant community data maintained by social networking system 104,where such pages are accessible by a web browser program operating on auser's computing device. Thus, any user having access to a givencommunity as defined by data stored in privileges database 116 can loadpart or all of such pages for display on the user's computing device. Inthe example of FIG. 1, a community's page or pages is accessible at aweb domain such as a URL including an org value identifying the specificorganization on behalf of which the community is maintained. This orgvalue can be a character such as a letter, number, symbol, or string ofcharacters identifying the specific organization with which thecommunity is affiliated. Thus, pages or other social network dataavailable to users 140 a in community 128 can be accessed at a URL suchas acme.force.com/community-acme1/. In this example of a URL, the string“acme” of “acme.force.com” can provide the org value, which identifiesAcme, Inc. by name. In some instances, the “acme” of “community-acme1”can provide the org value identifying Acme, Inc. Acme, Inc. can haveother web pages available to the general public, for example, at the URLacme.com, which is a different root domain than the acme.force.comaddress at which community-specific pages are provided.

The page or pages maintained by the social networking system 104 forcommunity 132 can be accessed at the URLorgb.force.com/community-orgb1/. As in the example of Acme, Inc., the“orgb” of “orgb.force.com” or the “orgb” of “community-orgb1” can be theorg value identifying Org B. One or more pages maintained on behalf ofcommunity 136 can similarly be accessed and identified with org valuesat the URL orgc.force.com/communityorgc1/.

As described in the examples below, when a user 140 d directly logs into a community using an appropriate login page at the community URL, andthe user is identified as a member of a particular community, the webbrowser program on the user's computing device can be automaticallyrouted to access a page at the URL specific to that user's community,such as acme.force.com/community-acme1/. The user can choose to navigatethrough additional pages accessible via the community or communities towhich the user belongs.

In addition, as explained in greater detail in the examples below, thenetwork address at which a community's pages are accessible can includebranding information identifying by a particular brand the communityand/or the organization on behalf of which the community is maintained.Thus, in FIG. 1, in the example of community 128, the URLacme.force.com/community-acme1/ includes the name “acme” twice, that is,at the root domain and as part of the sub-domain identifying community128. Such branding information can identify products and/or servicesprovided by organization in some instances. Thus, a URL at which pagesof community 128 are maintained can be customized to include names ofbrands recognizable to users having dealings with that organization,regardless of whether the users are employees, customers, partners orhave other relationships with a particular organization.

FIG. 2 shows a flowchart of an example of a computer implemented method200 for providing access to communities in an online social network,performed in accordance with some implementations. In FIG. 2, at block204, when a user 140 d of FIG. 1 logs in to a community at the communityURL, a computing device such as server 108 a receives a user ID from acomputing device 144 operated by user 140 d. For example, user 140 d cantype his or her ID and password into an appropriate community login pagedisplayed as a GUI on the display of device 144. At block 208, one ofthe servers 108 of social networking system 104 accesses user IDdatabase 112 to identify the user ID received from computing device 144in one or more lists of user IDs of various communities, such as tables120 and 124.

Thus, at block 212, when the user ID received from user 140 d isidentified, for example, as one of the IDs of users belonging to a firstcommunity 128, access to community 128 is provided via computing device144. The access provided at block 212 can be defined in terms ofprivileges to access designated data stored on behalf of community 128and/or to take one or more actions permitted to members of the community128, as defined by privilege information stored in privileges database116. For example, when the user 140 d is identified as an employee ofAcme, Inc., privilege information stored in database 116 may indicatethat user 140 d is able to access user profiles of other members ofcommunity 128, access community-specific files such as .xls spreadsheetsand .doc files, for instance, in the form of expense reimbursementrequests and travel requests, as well as take actions such as postingmessages on a community feed of community 128, posting messages on wallsof users 140 a, and following users 140 a and records stored by socialnetworking system 104 in association with community 128. That is, whenthe user 140 d makes an appropriate request for such data or to takesuch action, for instance, through an appropriate GUI displayed oncomputing device 144, such a request is transmitted to a server 108 ofsocial networking system 104, and the server 108 issues an appropriateresponse to computing device 144 acknowledging or denying the request inaccordance with privilege information stored in database 116. Requesteddata, which the user has the right to access, can thus be transmittedback to computing device 144. For instance, profile data of one or moreusers 140 a and/or community-specific file data can be transmitted froma server 108 to device 144 for viewing and further interaction by user140 d.

In FIG. 2, at block 216, during a browsing session, user 140 d maysubmit a request via computing device 144 to access a second communitymaintained on behalf of the same organization, Acme, Inc., or on behalfof a different organization, such as Org B of FIG. 1. At block 220,similar to block 208 described above, a server 108 in social networkingsystem 104 checks a list of user IDs of members of the second communityto determine whether the same user ID received at block 204 from user140 d is included in the list. At block 222, when the ID of user 140 dcannot be identified in the list of user IDs of users belonging to thesecond community, the server 108 sends a response to computing device144 indicating that access to the second community has been denied. Thecontent of such a response can be displayed in an appropriate GUI on thedisplay of computing device 144.

Returning to block 220, when the user ID of user 140 d is identified inthe list of members of the second community, at block 224, a server orservers 108 in social networking system 104 provides access to thesecond community. As described above with reference to community 128maintained on behalf of Acme, Inc., privilege information maintained indatabase 116 can be customized to define certain rights and restrictionsof members of the second community to access social network data andinitiate one or more actions, as described in greater detail below. Forexample, privilege information maintained in database 116 can identifyuser 140 d as either an internal or external user of the organization onbehalf of which the second community is maintained. Thus, appropriateaccess rights and restrictions can be assigned to internal or externalusers of the organization. For example, the user 140 d may be aninternal user of Org A and have a corresponding set of rights andrestrictions with community 128, while the same user may be an externaluser of Org B and, thus, have a different set of rights and restrictionswith community 132.

In one example, an app server 3288 in the on-demand service environment3200 of FIGS. 32A and 32B described below includes one or moreprocessors configured to perform part or all of blocks 204-224 of FIG.2. In other instances, one or more other computing devices of FIGS. 32Aand 32B such as user systems 12 and/or other servers retrieve, process,and exchange data to cooperate with app server 3288 to perform theblocks. When user input data is submitted from a user, such data can bereceived by a server over a data network from a user operating a usersystem 12 as shown in FIGS. 31A and 31B described below. In otherinstances, such data is received from a proxy server on behalf of a useror other data source. Various implementations of method 200 of FIG. 2are possible, such that any of the servers described below withreference to FIG. 32B or other computing devices disclosed herein can beconfigured to receive, process, and output data in accordance withmethod 200.

FIG. 3 shows a system diagram of an example of a social networkingenvironment 300 with communities according to some implementations.While FIG. 1 shows a single social networking system 104 providingaccess to the various communities, the environment of FIG. 3 includes asecond social networking system 304 in addition to social networkingsystem 104 as generally described above. The social networking system304 includes one or more servers 308 in communication with one or morestorage mediums 312 configured to store user IDs, user profiles, andadditional social network data appropriate for social networking system304.

In the example of FIG. 3, social networking system 104 maintains anumber of communities: community 316 of users 320 a, community 324 ofusers 320 b and a user 320 d, and community 328 of users 320 c. In thisexample, both communities 316 and 324 are maintained on behalf of thesame organization, Org A. In this example, community 328 is maintainedon behalf of Org B. In FIG. 3, social networking system 304 provides oneor more social networking services to users having user accounts orprofiles on system 304, including users 320 d. In FIG. 3, a user IDdatabase 332 of social networking system 104 maintains one or more userID mapping tables 400 as an alternative or in addition to user ID tables120 and 124 described above with reference to FIG. 1.

In FIG. 3, the user ID mapping table 400 can be used to identify one ormore communities maintained by social networking system 104 of which auser 140 d is a member. In addition, in the example of FIG. 3, the userID mapping table 400 can be configured to identify any additional socialnetworking systems such as system 304, at which user 140 d may have auser ID. When a user 140 d logs in to any community hosted at socialnetworking system 104, the user ID mapping table 400 can be accessed toidentify the user as a member of one or more other communities 316, 324and 328 maintained by social networking system 104. Thus, the user canbe automatically logged in, that is, without further input from theuser, to the other communities of which the user is a member. In anotherexample, the same user ID which a user submits to log in to his or heruser account with an organization's intranet can be used toautomatically log that user in to any communities maintained on behalfof the organization.

FIG. 4 shows an example of a user identity (ID) mapping table 400identifying communities to which a user can be provided access,according to some implementations. In FIG. 4, the user ID mapping table400 includes columns identifying any number of social networking systemsand any communities maintained by such systems. In this example, table400 identifies three respective social networking systems in columns404, 408 and 412. Two communities identified in columns 416 and 420 aremaintained by System 1, identified in column 404. Also, a communityidentified in column 424 is maintained by System 2 of column 408. Inthis example, System 3 identified in column 412 is a public systemaccessible by various users having accounts on such a system.

In FIG. 4, the user ID mapping table 400 can be configured to have rowsidentifying the user ID or IDs of a particular user used to gain accessto any of the social networking systems and/or communities identified inthe columns of table 400. A user can be able to log in to multipledifferent communities using the same single ID, for instance, in theform of a Chatter® user name, or in the form of an e-mail address usedto access that user's account on LinkedIn° or Facebook®. In otherinstances, a particular user can have different IDs needed to log in orgain access to different communities and/or social networking systems.Thus, in this example, a user Bill Smith identified in row 428 has auser profile with System 1 and community 1A maintained by System 1. Inthis instance, the same e-mail address, bsmith@acme.com is stored infields under columns 404 and 416. The same e-mail address,bsmith@acme.com, is used to access System 3 of column 412 as shown inrow 428. Thus, in the case of Bill Smith, a single user ID in the formof Bill's e-mail address can provide access to various social networkingsystems and one or more communities maintained on behalf of suchsystems.

In FIG. 4, in row 432, a user, Tom Jones, has a first user profile withSystem 1 and a second user profile with System 2. In this instance, TomJones is also a member of communities 1A and 1B maintained by System 1and community 2 maintained by System 2. As shown in row 432, the samee-mail address, tjones@ABC.com, is stored under the appropriate columnsto identify Tom as a member of those social networking systems andcommunities. As shown in row 436, in some instances, it can be desirableto store different user IDs associated with the same user to allow thatuser to directly log in to different communities and/or socialnetworking systems. In this example, Susan Nelson, a salesrepresentative for Media One, Inc., has user profiles on Systems 1, 2and 3 with different user IDs used to access each system. As indicatedin row 436, one or more servers receiving one of Susan's IDs can usetable 400 to log her in to System 1 using her e-mail address specific toSystem 1, in this case, snelson@media1.com.

Thus, returning to FIG. 3, when a user 140 d provides a user ID to login directly to a community hosted by social networking system 104 at thecommunity URL, identification of the provided user ID in a row of userIDs in table 400 can allow one or more servers to retrieve other userIDs for the same user to automatically provide access to additionalcommunities hosted at social networking system 104. Thus, for example,when a user logs in to a Burberry® community hosted at social networkingsystem 104 of FIG. 3, that user can be automatically logged in to othercommunities 316, 324 and 328 using an appropriate mapping table such astable 400 of FIG. 4.

Returning to FIG. 1, various types of database tables can be structuredto maintain appropriate privilege information in privileges database116. FIG. 5 shows an example of a privileges table 500 identifyingrights and restrictions of users to access data and initiate actions inone or more communities according to one or more attributes, accordingto some implementations. In FIG. 5, rights and restrictions can bedefined and customized in terms of various attributes, including theidentity of a particular organization on behalf of which a community ismaintained, a particular community of which a user is a member, a typeof user in the community, such as an internal user or an external user,as well as one or more roles a user in a community can have.

In FIG. 5, by way of illustration, privileges table 500 includes aprivileges column 504 specifying whether a user's rights to access dataand initiate actions are limited or unlimited according to variousattributes as mentioned above. That is, the ability for a particularuser to access and retrieve social network data and initiate varioussocial networking actions can be defined as unlimited or limited interms of one or more restrictions. Limited privileges with respect tosocial network data and/or actions can be defined on a per-attribute,per-user, per-data and/or per-action basis as described in greaterdetail below with reference to FIGS. 6 and 7. Examples of social networkdata with respect to which privileges can be uniquely defined andcustomized include particular names of records or types of records,particular user profiles or types of user profiles, particular statusesof user profiles, names of groups, particular types and statuses ofgroups, as well as CRM objects and various other constructs maintainedby a social networking system. Examples of types of CRM objects includecases, accounts, opportunities, leads and contacts. Such CRM objects canbe identified by name, type and/or status. Examples of particular socialnetworking actions with respect to which a user can have unlimited orlimited privileges include the ability to communicate with other usersvia one or more feeds, interact with particular records or types ofrecords via one or more feeds, interact with one or more tasks, interactwith one or more business processes, interact with CRM data, followusers, follow records, upload files, follow groups, join groups, creategroups, follow organizations and create communities.

Returning to the example of FIG. 5, privileges can be defined andcustomized according to an attribute such as the identity of aparticular organization and/or community with which a given user may beaffiliated. For example, column 508 identifies communities A-1, A-2 andA-3, all of which are specific to Org A. With a particular community ofa particular organization, as shown in column 512, a user's privilegeswith respect to data or actions can be categorized according to usertype. For example, as shown in column 512, community 1 of Org A has bothinternal and external users, as shown in row 516. The “internal” or“external” type of a user can refer to the user's relationship with thecommunity and/or organization identified in column 508. Thus, aninternal user of community 1 of Org A may be an employee of Org A. Inanother example, different rights and restrictions are set up andmaintained for internal and external users of community 1, regardless ofwhich organization community 1 is affiliated with. As shown in row 520,some communities and Orgs have no specified user type or role, such ascommunity 2 of Org A, which is a public community.

In FIG. 5, as shown in column 524, the privileges of a particular usercan be further defined in terms of the user's role in a community and/ororganization. Thus, in the example of row 516, employees of Org A haveunlimited rights to access data and initiate actions in a socialnetworking system in which community 1 is maintained. In the example ofcommunity 1 of Org A as shown in column 524 and row 516, other usershaving a customer or partner role, who are considered external users ofOrg A and community 1, also have unlimited rights to access and interactwith data and initiate actions in social networking system 104, as shownin column 504. In this example, members of the public community 2 of OrgA also have unlimited rights with respect to social network data andactions in the social networking system providing community 2, as shownin row 520 and column 504 of FIG. 5.

In another example, community 3 of Org A, as shown in row 528, has bothinternal and external users as shown in column 512. In community 3,internal users include both employees and partners of Org A. Incommunity 3 of Org A, even though employees and partners are consideredinternal users of Org A, these different roles carry differentprivileges, as shown in fields 532 and 536. In field 532, employees haveunlimited privileges with respect to social network data and actions. Asshown in field 536, partners of community 3 of Org A have limited accessto certain social network data and unlimited privileges to otherwiseinitiate actions in the social networking system providing community 3on behalf of Org A. As described in greater detail below, when rightsare restricted in some manner, that is, when privileges are limited asin the case of a partner's rights with respect to social network data incommunity 3 of Org A, an access model can be set up and customized tospecify particular and restrictions for accessing and interacting withsuch data. Access models are described in greater detail in the examplesbelow. Returning to FIG. 5, customers, who are considered external usersof community 3 of Org A, as shown in row 528, have restrictions on theirrights to access certain social network data and on their rights toinitiate one or more actions, as defined in an appropriate access model,as show in field 540.

FIG. 6 shows an example of a privileges table 600 identifying differentaccess models governing permissions of users to access data and initiateactions in one or more communities according to one or more attributes,according to some implementations. As shown in table 600, in someimplementations, access models identified in column 604 can bedifferentiated from each other according to one or more attributes asdescribed above with respect to FIG. 5 in addition to other attributes.In this example, various access models are configured according to thetype of community such as private or public in column 632, theparticular organization with which a community is affiliated in column636, a user type in column 640, and a user role in column 644.

In FIG. 6, a community column 608 identifies any number of communitiesaccessible through a social networking system. In this example,community column 608 identifies five communities in rows 612-628. Inthis example, communities A-1 and A-2 are both affiliated with Org A,community 2 is specific to Org C, community 3 is specific to Org B, andcommunity 4 is specific to Org D. In the case of communities A-2 and 2,a user type and a user role in columns 640 and 644 are not specified.This is because communities A-2 and 2 are public communities, whereusers have the same rights and restrictions regardless of their type orrole.

In FIG. 6, as shown in row 624, an access model in column 604 can bespecific to community 3, which is a private community maintained onbehalf of organization B, and where the rights and restrictions of theaccess model are specific to customers, who are external users ofcommunity 3. By the same token, as shown in row 628, a different accessmodel can be assigned to partners of private community 4, where suchpartners are internal users of Org D. The table 600 of FIG. 6 isintended to show non-limiting examples of the different access models,which can be defined and customized according to the various attributesidentified in columns 608, 632, 636, 640 and 644. Those skilled in theart will appreciate that various additional access models can beconfigured and maintained in additional rows of table 600, whichprovides a non-exhaustive listing of access models in column 604.

FIG. 7 shows an example of an access model customization window 700 asdisplayed in a graphical user interface (GUI) on a display device,according to some implementations. In FIG. 7, the access model window700 allows a system administrator or authorized community member tocustomize the rights and restrictions a user has to initiate actions andretrieve social network data in one or more communities as mentionedabove. In this example, a specific type of user can be specified infield 704, and a particular role of the user can be specified in field708. Thus, customized selections described below can be stored on asuitable storage medium, for instance, in privileges database 116 ofFIG. 1, to maintain customized rights and restrictions for particularuser types and roles in a given community and/or organization.

In this example, access model window 700 includes an actions pane 712with a list of actions available to external users who are partners, asindicated in fields 704 and 708. A data pane 716 identifies particulartypes of social network data, to which external users who are partnersof a given community and/or organization can be granted access. In thisexample, “feed-based communication” selection 720 has been selectedalong with “users” sub-selection 724 to allow partners to communicatewith other users using one or more feeds available to members of a givencommunity. For example, clicking on selection 720 and sub-selection 724allows a partner to post and comment on posts in a community feed.Selection 728, “task interaction”, allows one to determine whetherpartners will be allowed to interact with tasks otherwise accessible andviewable in a particular community. In this example, selection 728 hasnot been checked, thus preventing partners from interacting with suchtasks. A “business process interaction” selection 732 has beenactivated, allowing partners to view and interact with businessprocesses otherwise available to members of a given community. A “CRMInteraction” selection 736 has not been activated, thus preventingpartners from interacting with CRM objects stored in the socialnetworking system hosting the community. A “following” selection 740allows a system administrator to grant rights to partners allowing themto follow one or more entities 744, such as users, records,organizations and groups. In this example, only the “users” and “orgs”sub-selections 748 and 752 have been selected, thus allowing partners tofollow users and organizations but preventing partners from followingrecords and groups. A “group management” selection 756 and a “communitymanagement” selection 760 can be selected to allow a particular user, apartner in this example, to have the right to create, manage and deletegroups and communities. In this example, selections 756 and 760 have notbeen checked, thus preventing partners from having such privileges.

In FIG. 7, in data pane 716, a system administrator or other user canselect particular data objects and types of objects to which aparticular user, a partner in this example, can have read and/or writeprivileges in a community. In this example, “group profiles” selection764 and “user profiles” selection 768 have been checked, thus allowingpartners to view profiles of groups and users who have allowed theirprofiles to be publicly viewable. In this example, write privileges forsuch data are not available to anyone outside of a group leader or userowning the profile. Sub-selections 770 a-770 d can be selected tospecify particular types of profile information to which a partner canhave access. In this example, sub-selections 770 a and 770 b have beenchecked, allowing one to access a name and e-mail address of a publicuser profile, while selections 770 c-770 e have not been checked, thuspreventing partners from accessing photos, phone numbers andbiographical information of a user profile. In other sub-selections ofuser profiles, a roles selection 772 includes a data entry field 776allowing a system administrator to specify one or more roles of usershaving profiles, which a partner can be granted access to view. Titlesselection 780 similarly provides a data entry field 784 to specifytitles of users having public profiles that a partner can be grantedaccess to view.

In FIG. 7, selection 784 specifies whether a partner will have access topublic records otherwise accessible through a given community. A “CRM”selection 788 includes sub-selections 790 a-790 e allowing a systemadministrator to specify in data entry fields 792 a-792 e the names ofcases, accounts, opportunities, leads and/or contacts to which a partnershall have access. In this example, sub-selections 790 a and 790 b havebeen checked, with no names of cases or accounts specified in fields 792a and 792 b. Thus, a partner will have general access to cases andaccounts accessible to members of the particular community. By the sametoken, sub-selections 790 c-790 e have not been checked, thus preventingpartners from viewing or otherwise interacting with opportunities, leadsand contacts. Selection 794 can be checked to grant access to files of aparticular group named in data entry field 796. In this example, this“group files” selection 794 has not been checked, thus preventingpartners from accessing any such files stored or accessible to membersof a particular group.

In FIG. 7, returning to user profiles selection 768 and sub-selections770 a-770 e, a level of visibility of user profiles can be defined forpartners of a community in terms of which types of information in users'profiles can be viewed. For example, it may be desirable in someinstances that partners be able to access names and phone numbers, whilein other instances, partners should be restricted from viewing anycontact information other than the user's name.

As mentioned above, communities can be accessed at custom domains, whichmay include the name and/or brand of an organization with which thecommunity is affiliated. In some instances, an organization activelymanaging or otherwise providing input to community pages may customizethe particular domain name appropriately. Thus, in the example of FIG.1, representatives of Acme, Inc. have customized the URL of community128 to be acme.force.com/community-acme1/. In the example of FIG. 3,where communities 316 and 324 are both affiliated with Org A, community316 can be accessed at the URL orga.force.com/community-orga1/, whilecommunity 324 can be accessed at the URLorga.force.com/community-orga2/. In FIG. 3, community 328 can have a URLcustomized by representatives of Org B as desired, for instance, toinclude a brand name of a product or service provided by Org B.

In FIGS. 1 and 3, when a user 140 d is using an appropriate computingdevice 144 with a web browser program to navigate among the variousavailable communities, some of the disclosed implementations provide fornavigation from one community to another for the same and differentorganizations as a seamless experience for the user. Applying some ofthe disclosed techniques, cookies and web browsing sessions can becreated and managed in a transparent and secure manner.

As described in greater detail below, in some implementations, during abrowsing session, a user's computing device can be directed orredirected to appropriate login pages at selected times when appropriatefor security purposes. For instance, a user 140 d through the user'scomputing device 144 may request access to a community, which the userhas not logged in to. In one example, in FIG. 3, a user may have loggedin to community 324 but not community 328. In such cases, when the userattempts to click through a page provided atorga.force.com/community-orga2/that links to data maintained atcommunity 328, that is at the URL orgb.force.com/community-orgb1/,security mechanisms can be implemented to ensure that the requestinguser should be granted access to such data at community 328. In this andother various examples, the disclosed techniques provide forestablishing, managing and checking browsing sessions between a user andone or more communities at appropriate times and, when desired forsecurity purposes, prompting a user to enter credentials in the form ofa user ID and/or password. In this way, using appropriate GUIs, userscan select and retrieve data resources available through communities towhich the user belongs and navigate with security mechanisms beingtriggered at appropriate times to confirm that the user should begranted access to such data.

FIG. 8 shows a flowchart of an example of a computer implemented method800 for providing communities in an online social network, performed inaccordance with some implementations. In FIG. 8, at block 804, one ormore database tables with user IDs identifying users belonging toparticular communities can be maintained, such as tables 120 and 124stored in user ID database 112 of FIG. 1 and user ID mapping table 400stored in user ID database 332 of FIG. 3.

In the example of FIG. 8, a user such as user 140 d of FIG. 3 hasalready established a browsing session with community 316, for instance,by logging into that community via one or more login pages provided tothe user's computing device, for instance, at theorga.force.com/community-orga1/ sub-domain. In this example, afterestablishing this first session with community 316, thus providingcomputing device 144 with at least partial access to social network dataaccessible at community 316, at block 808, a server 108 in socialnetworking system 104 receives a request from computing device 144 toaccess another community such as community 324, also operated on behalfof Org A. In response to receiving such a request, at block 812, aserver 108 in social networking system 104 identifies the first session,for instance, by reading a cookie identifying the first session that wasdelivered to user 140 d's computing device 144 when the first sessionwith the community 316 was established.

In FIG. 8, at block 814, after the first session has been identified, atblock 814, a server 108 in social networking system 104 is configured todetermine whether the first session is still valid. One or moreprocessing operations can be performed at block 814 to check for one ora combination of conditions indicating that the first session is valid,as described in greater detail below with reference to FIGS. 9 and 10.At block 816, if the session with community 316 has timed out or isotherwise invalid, the request to access the second community is denied,for example, by delivering an appropriate response to computing device144.

Returning to block 814, when the first is determined to be valid, atblock 818, the request can be granted; that is, a second browsingsession between computing device 144 and community 324 can be initiated.One or more databases at social networking system 104 can be configuredto store and maintain identifications of sessions between a given user'scomputing device and any number of communities accessible via socialnetworking system 104. In some instances, as additional sessions areinitiated for a user's computing device after determining that one ormore valid sessions exist between that user's computing device and othercommunities, the identifications of the additional sessions can belinked, for example, in a parent-child hierarchy. For example, onesession can be identified as a parent or child of another sessiondetermined to be valid at block 814. The parent-child hierarchyrepresents one of various examples for identifying and managingconcurrent sessions that a user may establish with various communitiesaccessible through a social networking system. In other examples, adatabase table similar to user ID mapping table 400 of FIG. 4 can bemaintained, with fields under the respective system and communitycolumns 404-420 indicating whether a session is active.

In FIG. 8, at block 820, since a session with community 324 has beenestablished, social network data accessible through community 324 can bedelivered to the user's computing device 144 upon request, that is,after determining that the user 140 d has the appropriate privileges toaccess such data, as indicated by an access model or other definition ofuser rights and restrictions for community 324 as described above.

In some instances, it can be desirable to maintain one or more browsingsessions in response to user activity with respect to a given community.That is, as time passes and there is inaction on the part of a user 140d in any of the various communities with which the user has establisheda browsing session, activity on one of the communities can refreshsessions in the other communities. Thus, at block 824, by way ofexample, when a user takes an action such as following another user orsubscribing to a record of community 324, such an action can bedetected. After confirming at block 828 that such user action isrequested by user 140 d, for example, by checking one or more cookiesstored at computing device 144, at block 832, sessions with othercommunities such as community 316 can be maintained. For instance, whena timeout condition is implemented at community 316, activity incommunity 324 can cause the clock on which the timeout condition isbased to be reset.

FIG. 9 shows a flowchart of an example of a computer implemented method900 for providing communities in an online social network, performed inaccordance with some implementations. In FIG. 9, at block 904, one ormore database tables are maintained to identify users who are members ofvarious communities as generally described above at block 804 of FIG. 8.In this example, the lists of user IDs identify communities associatedwith different organizations. Thus, for example, as described above withreference to FIG. 3, a user ID mapping table 400 can identifycommunities 324, 328 and 336 in addition to community 316.

At block 908, a server 108 in social networking system 104 receives arequest to access community 324, 328 or 336 from computing device 144operated by user 140 d. For example, a user browsing a feed provided bycommunity 316 may see a feed item including a link to a file stored formembers of community 324 or 328. In another example, a user browsingsuch a feed in community 316 may wish to view a user profile of a userwho submitted a post to the feed of community 316. The request of block908 can be in the form of a mouse click or other selection made in a GUIto access data of another community or take some other action withrespect to the other community.

At block 912, in response to receiving such a request at block 908, aserver in social networking system 104 is configured to determinewhether the user's computing device 144 has access to another one of thecommunities. One or more conditions can be checked to make thisdetermination at block 912. For example, a server 108 can check whethera browsing session exists between the user's computing device 144 andcommunity 316. If such a session exists, the server can attempt toauthenticate that session, for example, using a session cookiepreviously stored at the user's computing device 144 when the sessionwith community 316 was established.

In some implementations, users can log in to multiple communitiesaffiliated with the same organization as desired to establish respectivesessions between the user's computing device and those communities. Insome instances, a cookie is issued for the root domain of theorganization, regardless of how many communities affiliated with thatorganization that the user has established sessions with. That is, insome instances, multiple sessions with different communities affiliatedwith the same organization can be identified by a single root domaincookie identifying the organization. Thus, in the example of FIG. 3, OrgA has at least two communities, community 316 and community 324. Whileuser 140 d can establish a separate session with each community 316 and324, in some implementations a cookie is only issued identifying theroot domain, orga.force.com, which is applicable to both communities 316and 324. Thus, in the example where a user has a session establishedwith community 316 and is requesting access to community 324, a server108 of social networking system 104 checks whether a cookie identifyingorga.force.com has been issued to the user's computing device 144. Ifthe cookie indicates that the session with community 316 is valid,method 900 can proceed to check other conditions, at block 926, such aswhether the user is identified in a table of user ID database 332 as amember of the community to which the user has requested access, in thiscase community 324. When such additional condition(s) is satisfied,method 900 can proceed to block 922 described below. At block 926, whenthe requesting user is not identified as a member of community 324, theuser is denied access, for instance, by a server 108 sending anappropriate message for display in a GUI on the user's computing device144.

Thus, for example, returning to block 912, when an external user hasalready logged in to community 316 and attempts to access a resource atcommunity 324, session management code can be executed at a server 108to identify a valid session with any community at the shared root domainof Org A, orga.force.com, as indicated by a cookie on the user'scomputing device 144. When a valid session with orga.force.com isidentified, at block 926, the server confirms that the user has rightsto access the requested resource at community 324 by confirming that therequesting user is a member of community 324.

Returning to block 912, when it is determined that computing device 144does not have access to community 316, a server 108 can provide the userwith an opportunity to log in to community 316. Thus, the server canprovide a branded login page at a custom network address to be loaded bythe browser program operating on computing device 144, at block 914. Thebranded login page can include branding information identifyingcommunity 316 and a prompt for a user ID and password to gain access tocommunity 316. For instance, the login page provided at block 914 caninclude product or service names of organization A and community 316.The login page at block 914 can be served from an appropriate custom URLsuch as the orga.force.com/community-orga1/ sub-domain. Such a loginpage can serve as an entry point to community 316 for both internal andexternal users, as described in greater detail in the examples below.

In FIG. 9, at block 916, the user ID to access community 316 is receivedfrom computing device 144. At block 918, a server 108 at socialnetworking system 104 determines whether the received user ID is one ofa list of user IDs of members of community 316. If the user ID is notidentified at block 918, processing can be terminated at block 920.Returning to block 918, if the user ID received at block 916 identifiesa member of community 316, at block 922, a browsing session providingaccess to the requested community 324 is established for computingdevice 144. Thus, at block 924, when a user 140 d requests socialnetwork data and/or actions available to members of community 324,appropriate data can be transmitted from a server 108 in socialnetworking system 104 to computing device 144.

While the examples described above in relation to FIG. 9 are in terms ofdifferent communities maintained on behalf of the same organization, thesame techniques can be applied to initiate, maintain and check thevalidity of browsing sessions established between a user's computingdevice 144 and various communities accessible through a socialnetworking system 104, including communities maintained on behalf ofother organizations. Database tables identifying and storing multiplesessions at a given time between the user's computing device 144 and thevarious communities, for instance, as identified in FIG. 3, can beprovided in a storage medium of social networking system 104. Thus, oneor more servers in a given social networking system 104 can identify andmanage user browsing sessions with communities maintained on behalf ofvarious organizations by expanding the number of cookies issued to acomputing device to identify such sessions. In situations where multipleorganizations and communities of such organizations are provided,separate cookies can be issued to identify individual sessions withparticular communities or identify groups of sessions according to theorganization on behalf of which the communities are maintained.

FIG. 10 shows a flowchart of an example of a computer implemented method1000 for initiating and managing sessions with communities in an onlinesocial network, performed in accordance with some implementations. InFIG. 10, at block 1002, a server 108 in social networking system 104 ofFIG. 3 is configured to detect that a user is not logged in to a firstcommunity, for example, when the user's computing device 144 hassubmitted a request to access the first community or a second communityaccessible through social networking system 104. At block 1004, a usernot being logged in to a particular community is one example of asituation in which a session has not been established or has timed outbetween the user's computing device and that community. At block 1004,in response to the user's request to access a community, the browserprogram on the user's computing device 144 is redirected to a pageprompting the user to indicate his or her type. For example, asmentioned above, a user's rights and restrictions to access certain dataand/or initiate certain actions in a given community can depend onwhether the user is an internal or external user of a given organizationand/or community. Thus, returning to block 1002, when the user hasrequested access to a record or other object stored, for example, atcommunity 324, the rights and restrictions of the user to access suchdata may depend on whether the user is of the internal or external type.Thus, at block 1004, the user's browser is redirected to a pageprompting the user to declare what kind of user he or she is. Forexample, the page provided at block 1004 can prompt the user to clickone of two options, “internal” or “external”. In this way, the browseron computing device 144 can be directed to an appropriate flow.

At block 1006, it is determined whether the user has indicated that heor she is an internal user or external user. In the example of FIG. 10,such types of users are handled in different manners. For example,external users can be provided with sessions and cookies identifyingonly a particular organization's root domain, such as orga.force.com. Inthis example, internal users will have separate sessions and cookiesestablished at both the root domain of orga.force.com and a domainoperated by social networking system 104 apart from the variouscommunities, such as na1.salesforce.com, when the social networkingsystem 104 is Chatter®, by way of example only.

In some implementations, to enable internal users to navigate betweenthe social networking system domain and the root domain of theorganization, servlets are provided to bridge the sessions with eachdomain. For example, a “CommunitiesLoginRedirect” servlet can be hostedat the root domain of Org A, that is, orga.force.com. Another servlet,“StandardLoginRedirect”, can be hosted at one or more servers of socialnetworking system 104. These servlets can be configured to detectsessions that may have been established between a user's computingdevice 144 and social networking system 104 and/or between computingdevice 144 and one or more communities. In addition, these servlets cancooperate with each other to initiate child or parent sessions asdesired with respect to existing sessions. In addition, the servlets canbe configured to pass session IDs identifying specific sessions.

At block 1006, when the user is identified as an internal user, thebrowser program operating on computing device 144 is redirected to theStandardLoginRedirect servlet running at social networking system 104.In this example, at block 1012, the StandardLoginRedirect servletdetects whether a session between the internal user's computing device144 and social networking system 104 exists. At block 1014, if such asession does not exist, the browser program operating on computingdevice 144 is redirected to a social networking system login page, suchas login.salesforce.com, with a target URL of the servletCommunitiesLoginRedirect hosted at orga.force.com. At block 1014, thelogin page displayed as a GUI on computing device 144 prompts the userfor credentials such as a user ID and password to gain access to socialnetworking system 104.

Following block 1014, if the login is successful at block 1024, theentered user ID and password confirm that the user has a profile or useraccount with social networking system 104. Thus, the method proceeds toblock 1028 at which a session of access with a first community, such ascommunity 324, is created by the CommunitiesLoginRedirect servlet andidentified as a child or parent with respect to the session the userestablished with social networking system 104 by providing theappropriate credentials at the login.salesforce.com page. For instance,a session cookie can be issued to computing device 144 at this point toidentify this session with community 324. Returning to block 1024,processing can be halted at block 1026 if the login is unsuccessful.

In FIG. 10, returning to block 1012, when a session with the socialnetworking system 104 is determined to be in existence, a server 108 insocial networking system 104 redirects the browser program operating oncomputing device 144 to the CommunitiesLoginRedirect servlet, which isconfigured to create a new session and issue one or more cookies atblock 1030.

Returning to block 1006, when the user is identified as an externaluser, at block 1040, the user's browser program is directed to acommunity login page at orga.force.com/community-orga2/of community 324to prompt the user for credentials such as a user ID and password. Atblock 1042, if the login is unsuccessful, processing can be terminatedat block 1046. At block 1042, if the login is successful, login codeexecuted at one or more servers of social networking system 104 isconfigured to detect the user ID received at block 1040 as beingincluded in one of the tables maintained at user ID database 332 andthus create a session between the user's computing device 144 and theroot domain, orga.force.com, or the specific community, in this case,orga.force.com/community-orga2. At block 1048, after an appropriatesession is established between the user's computing device 144 andcommunity 316, the browser program operating on computing device 144 canbe redirected to the requested resource stored at theorga.force.com/community-orga2/sub-domain. Thus, external users canaccess resources stored at orga.force.com/community-orga2/without havingto go through a generic login process for logging in to the socialnetworking system 104.

FIGS. 11-30 show examples of pages in the form of GUIs as displayed ondisplay devices for interacting with communities in an online socialnetwork, according to some implementations. In one example of a usecase, a user, Eddie, is a customer of Charles, an organization providinginvestment services. Returning to FIG. 3, Eddie uses his computingdevice 144 to navigate to a public website operated by or on behalf ofCharles, such as charles.com. Eddie is browsing the Charles website tosearch for information on international tax implications when investingfor retirement. In this example, Eddie is having difficulty identifyingany useful information on the public Charles website. Thus, Eddiedecides to log in to a Charles customer community 316 maintained by asocial networking system 104 on behalf of Charles.

As shown in FIG. 11, Eddie can navigate to a URL including a Charleslogo 1102, where Eddie is provided with a log-in screen 1100 promptinghim to enter a user ID and password in fields 1104 and 1108. Upon asuccessful log in, as shown in FIG. 12, Eddie's computer 144 is directedto a Charles community homepage 1200 hosted by social networking system104. At page 1200, Eddie can edit his profile using tab 1204, accessaccounts using tab 1208, and retrieve statements using tab 1212. Inaddition, Eddie's customer homepage 1200 includes a community feed 1216,which includes posts from customer service representatives and otheremployees of the Charles organization as well as record updates andother information updates regarding objects to which customers haveaccess in this Charles community. As shown in FIG. 13, when Eddieaccesses his profile page 1300 by clicking on tab 1204, Eddie isprompted with a notification 1304 to link his Charles user profile withone or more social networking systems identified in pane 1308. Thus, inFIG. 14, Eddie can enter a Facebook®, Twitter®, LinkedIn® or Chatter®user ID and password in pop-up window 1404 to be stored in one or moreuser ID database tables maintained to identify members of the Charlescommunity, for example, as described above with reference to FIGS. 1-4.That is, in the example of FIG. 4, the same user ID and password used toaccess a social networking system such as LinkedIn® or Facebook® can beused to also access the Charles community.

As shown in FIG. 15, by being a customer of the Charles organization,Eddie is able to access and load pages identifying customer servicerepresentatives such as Mary Lin, for instance, in the form of MaryLin's profile page 1500. In this example, Eddie enters a question 1504in a publisher component 1508 displayed as part of Mary's profile page.When Eddie clicks an ask button 1512, the question 1504 is posted toMary's profile feed 1604, as shown in FIG. 16. Mary can then enter acomment 1608 in response to Eddie's post 1504, and both the post 1504and comment 1608 are presented as feed items in profile feed 1604 asshown in FIG. 16. When Eddie returns to his updated profile page 1700,as shown in FIG. 17, Eddie's profile feed 1216 has been updated toinclude a record update 1704 notifying Eddie that Mary Lin has created aCRM object in the form of a case to work on Eddie's question and trackthe progress of her investigation. Other customer representatives whoare employees of the Charles organization can automatically be notifiedwhen such a CRM object is created in this manner, for example, by havingrecord update 1704 automatically posted to their respective news feeds.

As shown in FIG. 18, when Mary Lin logs in to the Charles community,Mary is presented with a different Charles homepage 1800 than thecustomer pages available to Eddie. This is because Mary is an employeeof the Charles organization, whereas Eddie is a customer. Thus, whilebranding names, themes and colors are common to both Eddie's and Mary'spresentations of the Charles community pages, different login processesand access models as described above can provide access to differentdata and different rights to take actions for Mary and Eddie. Forexample, as shown in FIG. 18, Mary has access to records in the form ofclients, files, cases and deals as presented in a pane 1804. However,when Eddie logs in to the Charles community and views pages at thecommunity URL, such records in region 1804 are hidden from Eddie'spresentation of Charles pages, in accordance with Eddie's restrictedprivileges. That is, any customers such as Eddie can be prevented fromaccessing records identifying confidential information of Charlesemployees and other customers. In this example, customer representativessuch as Mary can click on a “My Clients” link 1808 to access a profilepage 1900 of a customer such as Eddie, as shown in FIG. 19. In thisexample, customer representatives such as Mary have unlimited privilegesto access Eddie's profile information and submit messages such as acomment 1904 on Eddie's profile feed 1908.

As shown in FIG. 20, other customer representatives Ivan Rothschild andGeorgia Masters, who have been automatically subscribed to the new casethat Mary created for Eddie, can automatically receive Mary's comment1904 in their news feeds and can submit their own comments 2004 aboutthe case, as shown in page 2000. In this example, customerrepresentatives, such as Mary, Georgia and Ivan are provided withprivate chat-room privileges to communicate and collaborate with eachother in real-time using a chat window 2104 as shown in FIG. 21. Eddie,as a customer of the Charles organization, has an access model withrestrictions preventing Eddie from viewing or otherwise being notifiedof such a chat among customer representatives.

After a solution is reached, as shown in FIG. 22, Mary can post anadditional comment 2204 including a proposed solution to the case thatMary created. In this example, the comment 2204 can be viewed by Eddiewhen he accesses his profile page. As shown in FIG. 23, Mary can thenupdate the status of the case to “Waiting on Customer”, which is one ofseveral status options available in a status window 2304. In thisexample, the status window 2304 is presented as a component of case page2300 identifying the particular case Mary created to address Eddie'squestion.

Mary, as a member of multiple communities, some of which are operated onbehalf of the Charles organization, can view an overview of thesevarious communities in a “My Communities” page 2400 as shown in FIG. 24.For example, Mary is a member of the “client support” communityidentified by tab 2408 and the “advisor” community identified by tab2412. Thus, Mary can monitor feeds of these various communities in therespective tabs 2408 and 2412. In addition, as shown in FIG. 25, Marycan click on the “manage profiles” selection to cause an appropriatepop-up window 2504 to be displayed in page 2500. In pop-up window 2504,Mary can maintain a primary set of profile information and select whichparts of the profile information to share with the respectivecommunities. Thus, in the example of FIG. 25, in the client supportcommunity, Mary has chosen to expose her email, phone, title and usagestats but hide her “about me” information.

Returning to FIG. 24, Mary can click on an appropriate tab 2408 or 2412to access a home page for the identified community and thus monitor thecommunity's feed and access files stored for that community. In thisexample, employees of the Charles organization such as Mary have accessmodels permitting them to take additional actions in a social networkingenvironment, such as creating communities, joining communities, creatinggroups, joining groups, creating records, and following organizations,records, and customers of the Charles organization. However, the accessmodel for an employee such as Mary prevents Mary from viewing userprofiles and accessing private records of executives of theorganization. Such access models can be customized as desired for theparticular organization, community and user, as explained above withreference to FIGS. 5-7.

In FIG. 26, a customer representative or other employee of the Charlesorganization can access a “Create New Community” selection 2604 on herMy Communities page to create a new community for the organization. Theright to create new communities can be provided to users with one ormore defined roles or one or more defined types, such as internal users,as desired by the particular organization. As shown in FIG. 27, in thisexample, clicking on the Create New Community selection 2604 causes apop-up window 2704 to be displayed as an overlay on the page. In thisexample the pop-up window 2704 navigates the user through the variousattributes of a community being created, such as the particular userswho will be invited to join or automatically be added to the community.Thus, the customer representative can identify customers using option2708, partners using option 2712, event attendees using option 2716, adesignated sales team using option 2720 and/or other employees usingoption 2724.

As shown in FIG. 28, an additional pop-up window 2804 displayed as anoverlay on the page allows the user setting up the community to enter acommunity name in field 2808 and a description of the community'spurpose in field 2812. The type of the community can be specified asprivate or public using “privacy” selections 2816. As shown in FIG. 29,additional customization options are available, using a pop-up window2904 to select themes 2908, branding data 2912, and colors and fonts2916 to customize the appearance of community pages. For instance, a“Charles” logo used to identify Charles products and services can beuploaded in the form of a JPEG image. In addition, as mentioned above, aURL for the community can be specified to include the name “Charles”and/or the names of various products and services offered by Charlesthat relate to the community's purpose. Thus, the URL can include brandnames to associate the community with the desired organizational data.

As shown in FIG. 30, the pages of a community can be further customizedto have a specified layout 3002 using pop-up window 3004 as well as havedesignated settings 3008, features 3012, tabs 3016 and site pages 3020,the URLs of which being customized as described above.

Additional examples of systems, apparatus, and methods are disclosedherein for implementing enterprise level social and business informationnetworking. Such implementations can provide more efficient use of adatabase system. For instance, a user of a database system may noteasily know when important information in the database has changed,e.g., about a project or client. Implementations can provide feedtracked updates about such changes and other events, thereby keepingusers informed.

By way of example, a user can update a record, e.g., an opportunity suchas a possible sale of 1000 computers. Once the record update has beenmade, a feed tracked update about the record update can thenautomatically be provided, e.g., in a feed, to anyone subscribing to theopportunity or to the user. Thus, the user does not need to contact amanager regarding the change in the opportunity, since the feed trackedupdate about the update is sent via a feed right to the manager's feedpage or other page.

Mechanisms and methods for providing systems implementing enterpriselevel social and business information networking are disclosed hereinwith reference to several implementations. Examples of database systemsare described and can provide a platform for tracking events related toa record, actions of a user, and messages about a user or record. Thedisclosed systems support various data structures of feeds, thecustomization of feeds, selection of records and users to follow,generation of feeds, and display of feeds in suitable presentations on auser's display device.

FIG. 31A shows a block diagram of an example of an environment 10 inwhich an on-demand database service can be used in accordance with someimplementations. Environment 10 may include user systems 12, network 14,database system 16, processor system 17, application platform 18,network interface 20, tenant data storage 22, system data storage 24,program code 26, and process space 28. In other implementations,environment 10 may not have all of these components and/or may haveother components instead of, or in addition to, those listed above.

Environment 10 is an environment in which an on-demand database serviceexists. User system 12 may be implemented as any computing device(s) orother data processing apparatus such as a machine or system that is usedby a user to access a database system 16. For example, any of usersystems 12 can be a handheld computing device, a mobile phone, a laptopcomputer, a work station, and/or a network of such computing devices. Asillustrated in FIG. 31A (and in more detail in FIG. 31B) user systems 12might interact via a network 14 with an on-demand database service,which is implemented in the example of FIG. 31A as database system 16.

An on-demand database service, implemented using system 16 by way ofexample, is a service that is made available to outside users, who donot need to necessarily be concerned with building and/or maintainingthe database system. Instead, the database system may be available fortheir use when the users need the database system, i.e., on the demandof the users. Some on-demand database services may store informationfrom one or more tenants into tables of a common database image to forma multi-tenant database system (MTS). A database image may include oneor more database objects. A relational database management system(RDBMS) or the equivalent may execute storage and retrieval ofinformation against the database object(s). Application platform 18 maybe a framework that allows the applications of system 16 to run, such asthe hardware and/or software, e.g., the operating system. In someimplementations, application platform 18 enables creation, managing andexecuting one or more applications developed by the provider of theon-demand database service, users accessing the on-demand databaseservice via user systems 12, or third party application developersaccessing the on-demand database service via user systems 12.

The users of user systems 12 may differ in their respective capacities,and the capacity of a particular user system 12 might be entirelydetermined by permissions (permission levels) for the current user. Forexample, where a salesperson is using a particular user system 12 tointeract with system 16, that user system has the capacities allotted tothat salesperson. However, while an administrator is using that usersystem to interact with system 16, that user system has the capacitiesallotted to that administrator. In systems with a hierarchical rolemodel, users at one permission level may have access to applications,data, and database information accessible by a lower permission leveluser, but may not have access to certain applications, databaseinformation, and data accessible by a user at a higher permission level.Thus, different users will have different capabilities with regard toaccessing and modifying application and database information, dependingon a user's security or permission level, also called authorization.

Network 14 is any network or combination of networks of devices thatcommunicate with one another. For example, network 14 can be any one orany combination of a LAN (local area network), WAN (wide area network),telephone network, wireless network, point-to-point network, starnetwork, token ring network, hub network, or other appropriateconfiguration. Network 14 can include a TCP/IP (Transfer ControlProtocol and Internet Protocol) network, such as the global internetworkof networks often referred to as the “Internet” with a capital “I.” TheInternet will be used in many of the examples herein. However, it shouldbe understood that the networks that the present implementations mightuse are not so limited, although TCP/IP is a frequently implementedprotocol.

User systems 12 might communicate with system 16 using TCP/IP and, at ahigher network level, use other common Internet protocols tocommunicate, such as HTTP, FTP, AFS, WAP, etc. In an example where HTTPis used, user system 12 might include an HTTP client commonly referredto as a “browser” for sending and receiving HTTP signals to and from anHTTP server at system 16. Such an HTTP server might be implemented asthe sole network interface 20 between system 16 and network 14, butother techniques might be used as well or instead. In someimplementations, the network interface 20 between system 16 and network14 includes load sharing functionality, such as round-robin HTTP requestdistributors to balance loads and distribute incoming HTTP requestsevenly over a plurality of servers. At least for users accessing system16, each of the plurality of servers has access to the MTS' data;however, other alternative configurations may be used instead.

In one implementation, system 16, shown in FIG. 31A, implements aweb-based customer relationship management (CRM) system. For example, inone implementation, system 16 includes application servers configured toimplement and execute CRM software applications as well as providerelated data, code, forms, web pages and other information to and fromuser systems 12 and to store to, and retrieve from, a database systemrelated data, objects, and Webpage content. With a multi-tenant system,data for multiple tenants may be stored in the same physical databaseobject in tenant data storage 22, however, tenant data typically isarranged in the storage medium(s) of tenant data storage 22 so that dataof one tenant is kept logically separate from that of other tenants sothat one tenant does not have access to another tenant's data, unlesssuch data is expressly shared. In certain implementations, system 16implements applications other than, or in addition to, a CRMapplication. For example, system 16 may provide tenant access tomultiple hosted (standard and custom) applications, including a CRMapplication. User (or third party developer) applications, which may ormay not include CRM, may be supported by the application platform 18,which manages creation, storage of the applications into one or moredatabase objects and executing of the applications in a virtual machinein the process space of the system 16.

One arrangement for elements of system 16 is shown in FIGS. 31A and 31B,including a network interface 20, application platform 18, tenant datastorage 22 for tenant data 23, system data storage 24 for system data 25accessible to system 16 and possibly multiple tenants, program code 26for implementing various functions of system 16, and a process space 28for executing MTS system processes and tenant-specific processes, suchas running applications as part of an application hosting service.Additional processes that may execute on system 16 include databaseindexing processes.

Several elements in the system shown in FIG. 31A include conventional,well-known elements that are explained only briefly here. For example,each user system 12 could include a desktop personal computer,workstation, laptop, PDA, tablet, smartphone, or any wireless accessprotocol (WAP) enabled device or any other computing device capable ofinterfacing directly or indirectly to the Internet or other networkconnection. The term “computing device” is also referred to hereinsimply as a “computer”. User system 12 typically runs an HTTP client,e.g., a browsing program, such as Microsoft's Internet Explorer browser,Netscape's Navigator browser, Opera's browser, or a WAP-enabled browserin the case of a cell phone, PDA or other wireless device, or the like,allowing a user (e.g., subscriber of the multi-tenant database system)of user system 12 to access, process and view information, pages andapplications available to it from system 16 over network 14. Each usersystem 12 also typically includes one or more user input devices, suchas a keyboard, a mouse, trackball, touch pad, touch screen, pen or thelike, for interacting with a graphical user interface (GUI) provided bythe browser on a display (e.g., a monitor screen, LCD display, etc.) ofthe computing device in conjunction with pages, forms, applications andother information provided by system 16 or other systems or servers. Forexample, the user interface device can be used to access data andapplications hosted by system 16, and to perform searches on storeddata, and otherwise allow a user to interact with various GUI pages thatmay be presented to a user. As discussed above, implementations aresuitable for use with the Internet, although other networks can be usedinstead of or in addition to the Internet, such as an intranet, anextranet, a virtual private network (VPN), a non-TCP/IP based network,any LAN or WAN or the like.

According to one implementation, each user system 12 and all of itscomponents are operator configurable using applications, such as abrowser, including computer code run using a central processing unitsuch as an Intel Pentium® processor or the like. Similarly, system 16(and additional instances of an MTS, where more than one is present) andall of its components might be operator configurable usingapplication(s) including computer code to run using processor system 17,which may be implemented to include a central processing unit, which mayinclude an Intel Pentium® processor or the like, and/or multipleprocessor units. Non-transitory computer-readable media can haveinstructions stored thereon/in, that can be executed by or used toprogram a computing device to perform any of the methods of theimplementations described herein. Computer program code 26 implementinginstructions for operating and configuring system 16 to intercommunicateand to process web pages, applications and other data and media contentas described herein is preferably downloadable and stored on a harddisk, but the entire program code, or portions thereof, may also bestored in any other volatile or non-volatile memory medium or device asis well known, such as a ROM or RAM, or provided on any media capable ofstoring program code, such as any type of rotating media includingfloppy disks, optical discs, digital versatile disk (DVD), compact disk(CD), microdrive, and magneto-optical disks, and magnetic or opticalcards, nanosystems (including molecular memory ICs), or any other typeof computer-readable medium or device suitable for storing instructionsand/or data. Additionally, the entire program code, or portions thereof,may be transmitted and downloaded from a software source over atransmission medium, e.g., over the Internet, or from another server, asis well known, or transmitted over any other conventional networkconnection as is well known (e.g., extranet, VPN, LAN, etc.) using anycommunication medium and protocols (e.g., TCP/IP, HTTP, HTTPS, Ethernet,etc.) as are well known. It will also be appreciated that computer codefor the disclosed implementations can be realized in any programminglanguage that can be executed on a client system and/or server or serversystem such as, for example, C, C++, HTML, any other markup language,Java™, JavaScript, ActiveX, any other scripting language, such asVBScript, and many other programming languages as are well known may beused. (Java™ is a trademark of Sun Microsystems, Inc.).

According to some implementations, each system 16 is configured toprovide web pages, forms, applications, data and media content to user(client) systems 12 to support the access by user systems 12 as tenantsof system 16. As such, system 16 provides security mechanisms to keepeach tenant's data separate unless the data is shared. If more than oneMTS is used, they may be located in close proximity to one another(e.g., in a server farm located in a single building or campus), or theymay be distributed at locations remote from one another (e.g., one ormore servers located in city A and one or more servers located in cityB). As used herein, each MTS could include one or more logically and/orphysically connected servers distributed locally or across one or moregeographic locations. Additionally, the term “server” is meant to referto a computing device or system, including processing hardware andprocess space(s), an associated storage medium such as a memory deviceor database, and, in some instances, a database application (e.g.,OODBMS or RDBMS) as is well known in the art. It should also beunderstood that “server system” and “server” are often usedinterchangeably herein. Similarly, the database objects described hereincan be implemented as single databases, a distributed database, acollection of distributed databases, a database with redundant online oroffline backups or other redundancies, etc., and might include adistributed database or storage network and associated processingintelligence.

FIG. 31B shows a block diagram of an example of some implementations ofelements of FIG. 31A and various possible interconnections between theseelements. That is, FIG. 31B also illustrates environment 10. However, inFIG. 31B elements of system 16 and various interconnections in someimplementations are further illustrated. FIG. 31B shows that user system12 may include processor system 12A, memory system 12B, input system12C, and output system 12D. FIG. 31B shows network 14 and system 16.FIG. 31B also shows that system 16 may include tenant data storage 22,tenant data 23, system data storage 24, system data 25, User Interface(UI) 30, Application Program Interface (API) 32, PL/SOQL 34, saveroutines 36, application setup mechanism 38, applications servers 50₁-50 _(N), system process space 52, tenant process spaces 54, tenantmanagement process space 60, tenant storage space 62, user storage 64,and application metadata 66. In other implementations, environment 10may not have the same elements as those listed above and/or may haveother elements instead of, or in addition to, those listed above.

User system 12, network 14, system 16, tenant data storage 22, andsystem data storage 24 were discussed above in FIG. 31A. Regarding usersystem 12, processor system 12A may be any combination of one or moreprocessors. Memory system 12B may be any combination of one or morememory devices, short term, and/or long term memory. Input system 12Cmay be any combination of input devices, such as one or more keyboards,mice, trackballs, scanners, cameras, and/or interfaces to networks.Output system 12D may be any combination of output devices, such as oneor more monitors, printers, and/or interfaces to networks. As shown byFIG. 31B, system 16 may include a network interface 20 (of FIG. 31A)implemented as a set of HTTP application servers 50, an applicationplatform 18, tenant data storage 22, and system data storage 24. Alsoshown is system process space 52, including individual tenant processspaces 54 and a tenant management process space 60. Each applicationserver 50 may be configured to communicate with tenant data storage 22and the tenant data 23 therein, and system data storage 24 and thesystem data 25 therein to serve requests of user systems 12. The tenantdata 23 might be divided into individual tenant storage spaces 62, whichcan be either a physical arrangement and/or a logical arrangement ofdata. Within each tenant storage space 62, user storage 64 andapplication metadata 66 might be similarly allocated for each user. Forexample, a copy of a user's most recently used (MRU) items might bestored to user storage 64. Similarly, a copy of MRU items for an entireorganization that is a tenant might be stored to tenant storage space62. A UI 30 provides a user interface and an API 32 provides anapplication programmer interface to system 16 resident processes tousers and/or developers at user systems 12. The tenant data and thesystem data may be stored in various databases, such as one or moreOracle databases.

Application platform 18 includes an application setup mechanism 38 thatsupports application developers' creation and management ofapplications, which may be saved as metadata into tenant data storage 22by save routines 36 for execution by subscribers as one or more tenantprocess spaces 54 managed by tenant management process 60 for example.Invocations to such applications may be coded using PL/SOQL 34 thatprovides a programming language style interface extension to API 32. Adetailed description of some PL/SOQL language implementations isdiscussed in commonly assigned U.S. Pat. No. 7,730,478, titled METHODAND SYSTEM FOR ALLOWING ACCESS TO DEVELOPED APPLICATIONS VIA AMULTI-TENANT ON-DEMAND DATABASE SERVICE, by Craig Weissman, issued onJun. 1, 2010, and hereby incorporated by reference in its entirety andfor all purposes. Invocations to applications may be detected by one ormore system processes, which manage retrieving application metadata 66for the subscriber making the invocation and executing the metadata asan application in a virtual machine.

Each application server 50 may be communicably coupled to databasesystems, e.g., having access to system data 25 and tenant data 23, via adifferent network connection. For example, one application server 50 ₁might be coupled via the network 14 (e.g., the Internet), anotherapplication server 50 _(N-1) might be coupled via a direct network link,and another application server 50 _(N) might be coupled by yet adifferent network connection. Transfer Control Protocol and InternetProtocol (TCP/IP) are typical protocols for communicating betweenapplication servers 50 and the database system. However, it will beapparent to one skilled in the art that other transport protocols may beused to optimize the system depending on the network interconnect used.

In certain implementations, each application server 50 is configured tohandle requests for any user associated with any organization that is atenant. Because it is desirable to be able to add and remove applicationservers from the server pool at any time for any reason, there ispreferably no server affinity for a user and/or organization to aspecific application server 50. In one implementation, therefore, aninterface system implementing a load balancing function (e.g., an F5Big-IP load balancer) is communicably coupled between the applicationservers 50 and the user systems 12 to distribute requests to theapplication servers 50. In one implementation, the load balancer uses aleast connections algorithm to route user requests to the applicationservers 50. Other examples of load balancing algorithms, such as roundrobin and observed response time, also can be used. For example, incertain implementations, three consecutive requests from the same usercould hit three different application servers 50, and three requestsfrom different users could hit the same application server 50. In thismanner, by way of example, system 16 is multi-tenant, wherein system 16handles storage of, and access to, different objects, data andapplications across disparate users and organizations.

As an example of storage, one tenant might be a company that employs asales force where each salesperson uses system 16 to manage their salesprocess. Thus, a user might maintain contact data, leads data, customerfollow-up data, performance data, goals and progress data, etc., allapplicable to that user's personal sales process (e.g., in tenant datastorage 22). In an example of a MTS arrangement, since all of the dataand the applications to access, view, modify, report, transmit,calculate, etc., can be maintained and accessed by a user system havingnothing more than network access, the user can manage his or her salesefforts and cycles from any of many different user systems. For example,if a salesperson is visiting a customer and the customer has Internetaccess in their lobby, the salesperson can obtain critical updates as tothat customer while waiting for the customer to arrive in the lobby.

While each user's data might be separate from other users' dataregardless of the employers of each user, some data might beorganization-wide data shared or accessible by a plurality of users orall of the users for a given organization that is a tenant. Thus, theremight be some data structures managed by system 16 that are allocated atthe tenant level while other data structures might be managed at theuser level. Because an MTS might support multiple tenants includingpossible competitors, the MTS should have security protocols that keepdata, applications, and application use separate. Also, because manytenants may opt for access to an MTS rather than maintain their ownsystem, redundancy, up-time, and backup are additional functions thatmay be implemented in the MTS. In addition to user-specific data andtenant-specific data, system 16 might also maintain system level datausable by multiple tenants or other data. Such system level data mightinclude industry reports, news, postings, and the like that are sharableamong tenants.

In certain implementations, user systems 12 (which may be clientsystems) communicate with application servers 50 to request and updatesystem-level and tenant-level data from system 16 that may involvesending one or more queries to tenant data storage 22 and/or system datastorage 24. System 16 (e.g., an application server 50 in system 16)automatically generates one or more SQL statements (e.g., one or moreSQL queries) that are designed to access the desired information. Systemdata storage 24 may generate query plans to access the requested datafrom the database.

Each database can generally be viewed as a collection of objects, suchas a set of logical tables, containing data fitted into predefinedcategories. A “table” is one representation of a data object, and may beused herein to simplify the conceptual description of objects and customobjects according to some implementations. It should be understood that“table” and “object” may be used interchangeably herein. Each tablegenerally contains one or more data categories logically arranged ascolumns or fields in a viewable schema. Each row or record of a tablecontains an instance of data for each category defined by the fields.For example, a CRM database may include a table that describes acustomer with fields for basic contact information such as name,address, phone number, fax number, etc. Another table might describe apurchase order, including fields for information such as customer,product, sale price, date, etc. In some multi-tenant database systems,standard entity tables might be provided for use by all tenants. For CRMdatabase applications, such standard entities might include tables forcase, account, contact, lead, and opportunity data objects, eachcontaining pre-defined fields. It should be understood that the word“entity” may also be used interchangeably herein with “object” and“table”.

In some multi-tenant database systems, tenants may be allowed to createand store custom objects, or they may be allowed to customize standardentities or objects, for example by creating custom fields for standardobjects, including custom index fields. Commonly assigned U.S. Pat. No.7,779,039, titled CUSTOM ENTITIES AND FIELDS IN A MULTI-TENANT DATABASESYSTEM, by Weissman et al., issued on Aug. 17, 2010, and herebyincorporated by reference in its entirety and for all purposes, teachessystems and methods for creating custom objects as well as customizingstandard objects in a multi-tenant database system. In certainimplementations, for example, all custom entity data rows are stored ina single multi-tenant physical table, which may contain multiple logicaltables per organization. It is transparent to customers that theirmultiple “tables” are in fact stored in one large table or that theirdata may be stored in the same table as the data of other customers.

FIG. 32A shows a system diagram illustrating an example of architecturalcomponents of an on-demand database service environment 3200 accordingto some implementations. A client machine located in the cloud 3204,generally referring to one or more networks in combination, as describedherein, may communicate with the on-demand database service environmentvia one or more edge routers 3208 and 3212. A client machine can be anyof the examples of user systems 12 described above. The edge routers maycommunicate with one or more core switches 3220 and 3224 via firewall3216. The core switches may communicate with a load balancer 3228, whichmay distribute server load over different pods, such as the pods 3240and 3244. The pods 3240 and 3244, which may each include one or moreservers and/or other computing resources, may perform data processingand other operations used to provide on-demand services. Communicationwith the pods may be conducted via pod switches 3232 and 3236.Components of the on-demand database service environment may communicatewith a database storage 3256 via a database firewall 3248 and a databaseswitch 3252.

As shown in FIGS. 32A and 32B, accessing an on-demand database serviceenvironment may involve communications transmitted among a variety ofdifferent hardware and/or software components. Further, the on-demanddatabase service environment 3200 is a simplified representation of anactual on-demand database service environment. For example, while onlyone or two devices of each type are shown in FIGS. 32A and 32B, someimplementations of an on-demand database service environment may includeanywhere from one to many devices of each type. Also, the on-demanddatabase service environment need not include each device shown in FIGS.32A and 32B, or may include additional devices not shown in FIGS. 32Aand 32B.

Moreover, one or more of the devices in the on-demand database serviceenvironment 3200 may be implemented on the same physical device or ondifferent hardware. Some devices may be implemented using hardware or acombination of hardware and software. Thus, terms such as “dataprocessing apparatus,” “machine,” “server” and “device” as used hereinare not limited to a single hardware device, but rather include anyhardware and software configured to provide the described functionality.

The cloud 3204 is intended to refer to a data network or plurality ofdata networks, often including the Internet. Client machines located inthe cloud 3204 may communicate with the on-demand database serviceenvironment to access services provided by the on-demand databaseservice environment. For example, client machines may access theon-demand database service environment to retrieve, store, edit, and/orprocess information.

In some implementations, the edge routers 3208 and 3212 route packetsbetween the cloud 3204 and other components of the on-demand databaseservice environment 3200. The edge routers 3208 and 3212 may employ theBorder Gateway Protocol (BGP). The BGP is the core routing protocol ofthe Internet. The edge routers 3208 and 3212 may maintain a table of IPnetworks or ‘prefixes’, which designate network reachability amongautonomous systems on the Internet.

In one or more implementations, the firewall 3216 may protect the innercomponents of the on-demand database service environment 3200 fromInternet traffic. The firewall 3216 may block, permit, or deny access tothe inner components of the on-demand database service environment 3200based upon a set of rules and other criteria. The firewall 3216 may actas one or more of a packet filter, an application gateway, a statefulfilter, a proxy server, or any other type of firewall.

In some implementations, the core switches 3220 and 3224 arehigh-capacity switches that transfer packets within the on-demanddatabase service environment 3200. The core switches 3220 and 3224 maybe configured as network bridges that quickly route data betweendifferent components within the on-demand database service environment.In some implementations, the use of two or more core switches 3220 and3224 may provide redundancy and/or reduced latency.

In some implementations, the pods 3240 and 3244 may perform the coredata processing and service functions provided by the on-demand databaseservice environment. Each pod may include various types of hardwareand/or software computing resources. An example of the pod architectureis discussed in greater detail with reference to FIG. 32B.

In some implementations, communication between the pods 3240 and 3244may be conducted via the pod switches 3232 and 3236. The pod switches3232 and 3236 may facilitate communication between the pods 3240 and3244 and client machines located in the cloud 3204, for example via coreswitches 3220 and 3224. Also, the pod switches 3232 and 3236 mayfacilitate communication between the pods 3240 and 3244 and the databasestorage 3256.

In some implementations, the load balancer 3228 may distribute workloadbetween the pods 3240 and 3244. Balancing the on-demand service requestsbetween the pods may assist in improving the use of resources,increasing throughput, reducing response times, and/or reducingoverhead. The load balancer 3228 may include multilayer switches toanalyze and forward traffic.

In some implementations, access to the database storage 3256 may beguarded by a database firewall 3248. The database firewall 3248 may actas a computer application firewall operating at the database applicationlayer of a protocol stack. The database firewall 3248 may protect thedatabase storage 3256 from application attacks such as structure querylanguage (SQL) injection, database rootkits, and unauthorizedinformation disclosure.

In some implementations, the database firewall 3248 may include a hostusing one or more forms of reverse proxy services to proxy trafficbefore passing it to a gateway router. The database firewall 3248 mayinspect the contents of database traffic and block certain content ordatabase requests. The database firewall 3248 may work on the SQLapplication level atop the TCP/IP stack, managing applications'connection to the database or SQL management interfaces as well asintercepting and enforcing packets traveling to or from a databasenetwork or application interface.

In some implementations, communication with the database storage 3256may be conducted via the database switch 3252. The multi-tenant databasestorage 3256 may include more than one hardware and/or softwarecomponents for handling database queries. Accordingly, the databaseswitch 3252 may direct database queries transmitted by other componentsof the on-demand database service environment (e.g., the pods 3240 and3244) to the correct components within the database storage 3256.

In some implementations, the database storage 3256 is an on-demanddatabase system shared by many different organizations. The on-demanddatabase system may employ a multi-tenant approach, a virtualizedapproach, or any other type of database approach. An on-demand databasesystem is discussed in greater detail with reference to FIGS. 31A and31B.

FIG. 32B shows a system diagram further illustrating an example ofarchitectural components of an on-demand database service environmentaccording to some implementations. The pod 3244 may be used to renderservices to a user of the on-demand database service environment 3200.In some implementations, each pod may include a variety of serversand/or other systems. The pod 3244 includes one or more content batchservers 3264, content search servers 3268, query servers 3282, fileforce servers 3286, access control system (ACS) servers 3280, batchservers 3284, and app servers 3288. Also, the pod 3244 includes databaseinstances 3290, quick file systems (QFS) 3292, and indexers 3294. In oneor more implementations, some or all communication between the serversin the pod 3244 may be transmitted via the switch 3236.

In some implementations, the app servers 3288 may include a hardwareand/or software framework dedicated to the execution of procedures(e.g., programs, routines, scripts) for supporting the construction ofapplications provided by the on-demand database service environment 3200via the pod 3244. In some implementations, the hardware and/or softwareframework of an app server 3288 is configured to execute operations ofthe services described herein, including performance of the blocks ofmethods described with reference to FIGS. 1-30. In alternativeimplementations, two or more app servers 3288 may be included andcooperate to perform such methods, or one or more other serversdescribed herein can be configured to perform the disclosed methods.

The content batch servers 3264 may handle requests internal to the pod.These requests may be long-running and/or not tied to a particularcustomer. For example, the content batch servers 3264 may handlerequests related to log mining, cleanup work, and maintenance tasks.

The content search servers 3268 may provide query and indexer functions.For example, the functions provided by the content search servers 3268may allow users to search through content stored in the on-demanddatabase service environment.

The file force servers 3286 may manage requests for information storedin the Fileforce storage 3298. The Fileforce storage 3298 may storeinformation such as documents, images, and basic large objects (BLOBs).By managing requests for information using the file force servers 3286,the image footprint on the database may be reduced.

The query servers 3282 may be used to retrieve information from one ormore file systems. For example, the query system 3282 may receiverequests for information from the app servers 3288 and then transmitinformation queries to the NFS 3296 located outside the pod.

The pod 3244 may share a database instance 3290 configured as amulti-tenant environment in which different organizations share accessto the same database. Additionally, services rendered by the pod 3244may call upon various hardware and/or software resources. In someimplementations, the ACS servers 3280 may control access to data,hardware resources, or software resources.

In some implementations, the batch servers 3284 may process batch jobs,which are used to run tasks at specified times. Thus, the batch servers3284 may transmit instructions to other servers, such as the app servers3288, to trigger the batch jobs.

In some implementations, the QFS 3292 may be an open source file systemavailable from Sun Microsystems® of Santa Clara, Calif. The QFS mayserve as a rapid-access file system for storing and accessinginformation available within the pod 3244. The QFS 3292 may support somevolume management capabilities, allowing many disks to be groupedtogether into a file system. File system metadata can be kept on aseparate set of disks, which may be useful for streaming applicationswhere long disk seeks cannot be tolerated. Thus, the QFS system maycommunicate with one or more content search servers 3268 and/or indexers3294 to identify, retrieve, move, and/or update data stored in thenetwork file systems 3296 and/or other storage systems.

In some implementations, one or more query servers 3282 may communicatewith the NFS 3296 to retrieve and/or update information stored outsideof the pod 3244. The NFS 3296 may allow servers located in the pod 3244to access information to access files over a network in a manner similarto how local storage is accessed.

In some implementations, queries from the query servers 3222 may betransmitted to the NFS 3296 via the load balancer 3228, which maydistribute resource requests over various resources available in theon-demand database service environment. The NFS 3296 may alsocommunicate with the QFS 3292 to update the information stored on theNFS 3296 and/or to provide information to the QFS 3292 for use byservers located within the pod 3244.

In some implementations, the pod may include one or more databaseinstances 3290. The database instance 3290 may transmit information tothe QFS 3292. When information is transmitted to the QFS, it may beavailable for use by servers within the pod 3244 without using anadditional database call.

In some implementations, database information may be transmitted to theindexer 3294. Indexer 3294 may provide an index of information availablein the database 3290 and/or QFS 3292. The index information may beprovided to file force servers 3286 and/or the QFS 3292.

As multiple users might be able to change the data of a record, it canbe useful for certain users to be notified when a record is updated.Also, even if a user does not have authority to change a record, theuser still might want to know when there is an update to the record. Forexample, a vendor may negotiate a new price with a salesperson ofcompany X, where the salesperson is a user associated with tenant Y. Aspart of creating a new invoice or for accounting purposes, thesalesperson can change the price saved in the database. It may beimportant for co-workers to know that the price has changed. Thesalesperson could send an email to certain people, but this is onerousand the salesperson might not email all of the people who need to knowor want to know. Accordingly, some implementations of the disclosedtechniques can inform others (e.g., co-workers) who want to know aboutan update to a record automatically.

The tracking and reporting of updates to a record stored in a databasesystem can be facilitated with a multi-tenant database system 16, e.g.,by one or more processors configured to receive or retrieve information,process the information, store results, and transmit the results. Inother implementations, the tracking and reporting of updates to a recordmay be implemented at least partially with a single tenant databasesystem.

The specific details of the specific aspects of implementationsdisclosed herein may be combined in any suitable manner withoutdeparting from the spirit and scope of the disclosed implementations.However, other implementations may be directed to specificimplementations relating to each individual aspect, or specificcombinations of these individual aspects.

While the disclosed examples are often described herein with referenceto an implementation in which an on-demand database service environmentis implemented in a system having an application server providing afront end for an on-demand database service capable of supportingmultiple tenants, the present implementations are not limited tomulti-tenant databases nor deployment on application servers.Implementations may be practiced using other database architectures,i.e., ORACLE®, DB2® by IBM and the like without departing from the scopeof the implementations claimed.

It should be understood that some of the disclosed implementations canbe embodied in the form of control logic using hardware and/or usingcomputer software in a modular or integrated manner. Other ways and/ormethods are possible using hardware and a combination of hardware andsoftware.

Any of the software components or functions described in thisapplication may be implemented as software code to be executed by aprocessor using any suitable computer language such as, for example,Java, C++ or Perl using, for example, conventional or object-orientedtechniques. The software code may be stored as a series of instructionsor commands on a computer-readable medium for storage and/ortransmission, suitable media include random access memory (RAM), a readonly memory (ROM), a magnetic medium such as a hard-drive or a floppydisk, or an optical medium such as a compact disk (CD) or DVD (digitalversatile disk), flash memory, and the like. The computer-readablemedium may be any combination of such storage or transmission devices.Computer-readable media encoded with the software/program code may bepackaged with a compatible device or provided separately from otherdevices (e.g., via Internet download). Any such computer-readable mediummay reside on or within a single computing device or an entire computersystem, and may be among other computer-readable media within a systemor network. A computer system, or other computing device, may include amonitor, printer, or other suitable display for providing any of theresults mentioned herein to a user.

While various implementations have been described herein, it should beunderstood that they have been presented by way of example only, and notlimitation. Thus, the breadth and scope of the present applicationshould not be limited by any of the implementations described herein,but should be defined only in accordance with the following andlater-submitted claims and their equivalents.

What is claimed is:
 1. A computer implemented method for providing communities of users in an online social network, the method comprising: maintaining a plurality of user identities (IDs) on one or more storage media, the user IDs including first user IDs identifying first users belonging to a first community associated with a first organization and second user IDs identifying second users belonging to a second community, the communities maintained in an online social network; receiving, at a server, a request to access the second community from a computing device associated with a user; determining that the computing device has established access to the first community; accessing the one or more storage media to determine that the user ID is one of the second user IDs; and sending, to the computing device, responsive to determining that the user ID is one of the second user IDs, social network data available to the second users.
 2. The method of claim 1, wherein determining that the computing device has established access to the first community includes: identifying a first session of access to the first community; and determining that the first session is valid.
 3. The method of claim 2, further comprising: initiating a second session of access to the second community responsive to determining that the first session is valid.
 4. The method of claim 3, wherein the second session has a child-parent relationship or a parent-child relationship with the first session.
 5. The method of claim 1, wherein one or more database tables on the one or more storage media stores: the user ID in association with a social networking system providing the user ID, the first user IDs, and the second user IDs.
 6. The method of claim 1, wherein a database table on the one or more storage media identifies the user ID as an internal user of the first organization and an external user of a second organization associated with the second community.
 7. The method of claim 1, wherein determining that the computing device has established access to the first community includes: determining that the user ID is one of the first user IDs.
 8. The method of claim 7, further comprising: initiating a first session of access to the first community responsive to determining that the user ID is one of the first user IDs.
 9. The method of claim 8, wherein initiating the first session of access includes: issuing, to the computing device, a cookie identifying the first session.
 10. The method of claim 9, wherein determining that the computing device has established access to the first community further includes: identifying the first session as being associated with the user ID; and authenticating the first session using the first session cookie.
 11. The method of claim 10, further comprising: initiating a second session of access to the second community responsive to determining that the user ID is one of the second user IDs.
 12. The method of claim 1, wherein the first users include one or more of: employees of the first organization, customers of the first organization, and partners of the first organization.
 13. The method of claim 12, wherein the employees, customers, and partners each have a respective set of privileges for a computing device to access social network data and initiate social networking actions available to users of the first community, each privileges set being defined by a respective user access model stored on a storage medium in association with the first community.
 14. The method of claim 13, wherein the user access model defines a first set of privileges for external users of the first organization and a second set of privileges for internal users of the first organization, the second set of privileges being different from the first set of privileges.
 15. One or more computing devices for providing communities of users in an online social network, the one or more computing devices comprising: one or more processors operable to execute one or more instructions to: interface with one or more storage media storing a plurality of user identities (IDs) including first user IDs identifying first users belonging to a first community associated with a first organization and second user IDs identifying second users belonging to a second community, the communities maintained in the online social network; determine that a computing device associated with a user has established access to the first community responsive to a request to access the second community, the request received from the computing device; access the one or more storage media to determine that the user ID is one of the second user IDs; and send, to the computing device, responsive to determining that the user ID is one of the second user IDs, social network data available to the second users.
 16. The one or more computing devices of claim 15, the one or more processors operable to execute one or more instructions to: identify a first session of access to the first community; and determine that the first session is valid.
 17. The one or more computing devices of claim 16, the one or more processors operable to execute one or more instructions to: initiate a second session of access to the second community responsive to determining that the first session is valid.
 18. The one or more computing devices of claim 15, wherein one or more database tables on the one or more storage media stores: the user ID in association with a social networking system providing the user ID, the first user IDs, and the second user IDs.
 19. The one or more computing devices of claim 15, wherein a database table on the one or more storage media identifies the user ID as an internal user of the first organization and an external user of the second organization.
 20. A non-transitory computer-readable storage medium storing instructions executable by a computing device to perform a method for providing communities of users in an online social network, the method comprising: interfacing with one or more storage media storing a plurality of user identities (IDs) including first user IDs identifying first users belonging to a first community associated with a first organization and second user IDs identifying second users belonging to a second community, the communities maintained in the online social network; determining that a computing device associated with a user has established access to the first community responsive to a request to access the second community, the request received from the computing device; accessing the one or more storage media to determine that the user ID is one of the second user IDs; and sending, to the computing device, responsive to determining that the user ID is one of the second user IDs, social network data available to the second users. 